feat(resourcemanager): persist the service limits for keyspaces

[JmPotato]

What problem does this PR solve?

Issue Number: ref #9296.

What is changed and how does it work?

Implement persistence for service limits in the resource manager. Service limits are now saved to storage when set and automatically loaded during initialization.

Check List

Tests

• Unit test
• Integration test

Release note

None.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lhy1024, rleungx

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [lhy1024,rleungx]

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:

• 2025-06-18 07:11:07.980350918 +0000 UTC m=+255720.703529900: ☑️ agreed by lhy1024.
• 2025-06-18 08:04:01.271686302 +0000 UTC m=+258893.994865284: ☑️ agreed by rleungx.

[JmPotato]

/retest

[codecov]

Codecov Report

Attention: Patch coverage is 56.81818% with 19 lines in your changes missing coverage. Please review.

Project coverage is 76.18%. Comparing base (49c177a) to head (3c22f15).
Report is 3 commits behind head on master.

❌ Your patch status has failed because the patch coverage (56.81%) is below the target coverage (74.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #9413      +/-   ##
==========================================
- Coverage   76.18%   76.18%   -0.01%     
==========================================
  Files         478      478              
  Lines       74794    74840      +46     
==========================================
+ Hits        56984    57019      +35     
- Misses      14282    14297      +15     
+ Partials     3528     3524       -4     

Flag	Coverage Δ
unittests	76.18% <56.81%> (-0.01%)	⬇️

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.