scheduler: fix scatter counter name

[HuSharp]

What problem does this PR solve?

Issue Number: Close #8125

What is changed and how does it work?

when execute curl -X POST 'http://127.0.0.1:10080/tables/test/t/scatter'

before

after

Check List

Tests

• Manual test (add detailed scripts or steps below)

Release note

None.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• lhy1024
• nolouch

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.

[lhy1024]

also pick to other branches

[HuSharp]

/check-issue-triage-complete

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.37%. Comparing base (de5bad3) to head (7da44ba).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #8124      +/-   ##
==========================================
- Coverage   77.39%   77.37%   -0.02%     
==========================================
  Files         471      471              
  Lines       61242    61252      +10     
==========================================
  Hits        47396    47396              
- Misses      10281    10291      +10     
  Partials     3565     3565              

Flag	Coverage Δ
unittests	77.37% <100.00%> (-0.02%)	⬇️

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

[JmPotato]

/merge

[ti-chi-bot]

@JmPotato: 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: 7da44ba

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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