mcs: fix participant name

[rleungx]

What problem does this PR solve?

Issue Number: Close #7336.

What is changed and how does it work?

Previously, in operator env, the primary name used the listen address which could be duplicated.

[2023/11/07 11:14:20.525 +00:00] [INFO] [server.go:267] ["campaign scheduling primary ok"] [campaign-scheduling-primary-name=http://0.0.0.0:2379]

Check List

Tests

• Manual test

Release note

None.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• CabinfeverB
• lhy1024

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.

[codecov]

Codecov Report

Merging #7335 (c20da40) into master (4457ac2) will increase coverage by 0.04%.
The diff coverage is 57.14%.

❗ Current head c20da40 differs from pull request most recent head 0e5fa13. Consider uploading reports for the commit 0e5fa13 to get more accurate results

@@            Coverage Diff             @@
##           master    #7335      +/-   ##
==========================================
+ Coverage   74.42%   74.46%   +0.04%     
==========================================
  Files         446      446              
  Lines       48433    48440       +7     
==========================================
+ Hits        36047    36072      +25     
+ Misses       9200     9185      -15     
+ Partials     3186     3183       -3     

Flag	Coverage Δ
unittests	74.46% <57.14%> (+0.04%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

[rleungx]

/merge

[ti-chi-bot]

@rleungx: 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: c20da40

[ti-chi-bot]

@rleungx: Your PR was out of date, I have automatically updated it for you.

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.

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.