*: fix exception when no tcp and http server created

[ywqzzy]

What problem does this PR solve?

Issue Number: close #7282

Problem Summary:
When no tcp and http server created, tiflash might have exception.

What is changed and how it works?

Allow tiflash to have no tcp and http server, just print an warning log.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
  As the issue said

➜  ~ tiup playground v7.1.0 --tiflash.config=~/tiflash.config
tiup is checking updates for component playground ...
A new version of playground is available:
   The latest version:         v1.16.0
   Local installed version:    v1.10.3
   Update current component:   tiup update playground
   Update all components:      tiup update --all

Starting component `playground`: /Users/bba/.tiup/components/playground/v1.10.3/tiup-playground v7.1.0 --tiflash.config=~/tiflash.config
Playground Bootstrapping...
Start pd instance:v7.1.0
Start tikv instance:v7.1.0
Start tidb instance:v7.1.0
Waiting for tidb instances ready
[127.0.0.1:4000](http://127.0.0.1:4000/) ... Done
Start tiflash instance:v7.1.0
Waiting for tiflash instances ready
Waiting for tiflash instances ready
[127.0.0.1:3930](http://127.0.0.1:3930/) ... Error
CLUSTER START SUCCESSFULLY, Enjoy it ^-^
To connect TiDB: mysql --comments --host [127.0.0.1](http://127.0.0.1/) --port 4000 -u root -p (no password)
To view the dashboard: http://127.0.0.1:2379/dashboard
PD client endpoints: [[127.0.0.1:2379](http://127.0.0.1:2379/)]
To view the Prometheus: http://127.0.0.1:9090/
To view the Grafana: http://127.0.0.1:3000/

• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• Lloyd-Pottiger
• SeaRise

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[ywqzzy]

/merge

[ti-chi-bot]

@ywqzzy: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: f485f35

[ywqzzy]

/run-all-tests

[ywqzzy]

/run-all-tests

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.1: #9221.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-5.4: #9222.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-5.3: #9223.