resource_group: don't accumulate tokens when burstlimit less than 0

[CabinfeverB]

What problem does this PR solve?

Issue Number: ref #7206

What is changed and how does it work?

We can find a large number from default resource group.

{"r_u":{"settings":{"fill_rate":2147483647,"burst_limit":-1},"state":{"tokens":29860685960413220,"last_update":"2023-12-27T08:19:16.269363735Z","initialized":true}}}

So don't accumulate tokens when burstlimit less than 0

Check List

Tests

• Unit test

Code changes

• Has the configuration change
• Has HTTP API interfaces changed (Don't forget to add the declarative for the new API)
• Has persistent data change

Side effects

• Possible performance regression
• Increased code complexity
• Breaking backward compatibility

Related changes

• PR to update pingcap/docs/pingcap/docs-cn:
• PR to update pingcap/tiup:
• Need to cherry-pick to the release branch

Release note

None.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• bufferflies
• 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.

[CabinfeverB]

@nolouch do we need cherry-pick?

[codecov]

Codecov Report

Merging #7626 (4c4ad7c) into master (baf4345) will decrease coverage by 0.08%.
The diff coverage is 90.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #7626      +/-   ##
==========================================
- Coverage   73.89%   73.82%   -0.08%     
==========================================
  Files         429      429              
  Lines       47345    47346       +1     
==========================================
- Hits        34986    34953      -33     
- Misses       9368     9399      +31     
- Partials     2991     2994       +3     

Flag	Coverage Δ
unittests	73.82% <90.00%> (-0.08%)	⬇️

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

[nolouch]

lgtm

[nolouch]

@nolouch do we need cherry-pick?

Yes, I think we need.

[nolouch]

/merge

[ti-chi-bot]

@nolouch: 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: da29fb5

[ti-chi-bot]

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

[ti-chi-bot]

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