TiFlash logs to directly display the name of the service conflicting with a port

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

https://asktug.com/t/topic/1040132/3

[2025/03/14 15:25:33.792 +08:00] [INFO] [SchemaSyncService.cpp:181] ["SchemaSyncService stopped"] [thread_id=1]
[2025/03/14 15:25:35.484 +08:00] [INFO] [Server.cpp:1070] ["Let tiflash proxy shutdown"] [thread_id=1]
[2025/03/14 15:25:35.484 +08:00] [INFO] [Server.cpp:1073] ["Wait for tiflash proxy thread to join"] [thread_id=1]
[2025/03/14 15:25:35.558 +08:00] [INFO] [Server.cpp:1075] ["tiflash proxy thread is joined"] [thread_id=1]
[2025/03/14 15:25:35.558 +08:00] [ERROR] [<unknown>] ["null context when constructing CivetServer. Possible problem binding to port."] [source=Application] [thread_id=1]
[2025/03/14 15:25:35.558 +08:00] [INFO] [<unknown>] ["shutting down"] [source=Application] [thread_id=1]
[2025/03/14 15:25:35.559 +08:00] [INFO] [BaseDaemon.cpp:307] ["Stop SignalListener thread"] [source=BaseDaemon] [thread_id=609]

reference link https://asktug.com/t/topic/1040132

2. What did you expect to see? (Required)

I want TiFlash logs to directly display the name of the service conflicting with a port when a port collision occurs, rather than just indicating that a port is problematic. Currently, I can only see that a port issue exists, which makes it inefficient to pinpoint the exact problem.

3. What did you see instead (Required)

N/A

4. What is your TiFlash version? (Required)

v7.5.5

Start by tracing the port-binding failure around Server.cpp and the CivetServer error shown in the report, then check how the affected service is configured and logged. Reproduce the collision described in the linked report and verify that the TiFlash log identifies the service conflicting with the port rather than only reporting a binding problem.