autoid_service: fix potential autoid decrease when leader change or close for AUTO_ID_CACHE=1 (#52602)

[ti-chi-bot]

This is an automated cherry-pick of #52602

What problem does this PR solve?

Issue Number: close #52600

Problem Summary:

What changed and how does it work?

1. reset map when a node become leader
2. add lock to protect the map in forceRebase when close

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)

See the steps in #52600
I'll file another PR to support http API, because it import new changes rather than simple bug fix.

• No need to test

  • I checked and no code files have been changed.

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

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Defined2014
Once this PR has been reviewed and has the lgtm label, please ask for approval from tiancaiamao, ensuring that each of them provides their approval before proceeding. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• pkg/autoid_service/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-05-07 01:58:11.651693049 +0000 UTC m=+927245.408828615: ☑️ agreed by Defined2014.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

❗ No coverage uploaded for pull request base (release-7.5@3df1fe2). Click here to learn what that means.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-7.5     #52999   +/-   ##
================================================
  Coverage               ?   72.0038%           
================================================
  Files                  ?       1410           
  Lines                  ?     409520           
  Branches               ?          0           
================================================
  Hits                   ?     294870           
  Misses                 ?      94806           
  Partials               ?      19844           

Flag	Coverage Δ
unit	72.0038% <100.0000%> (?)

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

Components	Coverage Δ
dumpling	53.9913% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	53.3610% <0.0000%> (?)