packaging/docs: replace deprecated rpc.batchlimit key

[odupontt]

Description

This PR fixes a real configuration correctness issue caused by a key mismatch between runtime config parsing and shipped templates/docs.

internal/cli/server/config.go now expects rpc.batch-request-limit, but multiple template files and the CLI example still used rpc.batchlimit.
If operators uncommented the old key, Bor silently ignored it and kept the default batch request limit (1000), which could lead to unexpected production behavior.

What was done:

1. Replaced rpc.batchlimit with rpc.batch-request-limit in all affected packaging templates.
2. Updated builder/files/config.toml to use the correct key.
3. Updated docs/cli/example_config.toml to keep docs/examples aligned with runtime behavior.
4. Kept the change minimal: key rename only, no default value changes, no runtime logic changes.

Changes

• Bugfix (non-breaking change that solves an issue)
• Hotfix (change that solves an urgent issue, and requires immediate attention)
• New feature (non-breaking change that adds functionality)
• Breaking change (change that is not backwards-compatible and/or changes current functionality)
• Changes only for a subset of nodes

Nodes audience

This change applies to all operators who rely on shipped Bor templates/examples.
It is not limited to a subset of nodes.

Checklist

• I have added at least 2 reviewer or the whole pos-v1 team
• I have added sufficient documentation in code
• I will be resolving comments - if any - by pushing each fix in a separate commit and linking the commit hash in the comment reply
• Created a task in Jira and informed the team for implementation in Erigon client (if applicable)
• Includes RPC methods changes, and the Notion documentation has been updated

Cross repository changes

• This PR requires changes to heimdall
  • In case link the PR here:
• This PR requires changes to matic-cli
  • In case link the PR here:

Testing

• I have added unit tests
• I have added tests to CI
• I have tested this code manually on local environment
• I have tested this code manually on remote devnet using express-cli
• I have tested this code manually on amoy
• I have created new e2e tests into express-cli

Manual tests

1. Verified old key is removed from repo templates/examples:
   • rg -n "rpc\.batchlimit" .
   • Result: no matches in templates/docs after this PR.
2. Verified new key is present where expected:
   • rg -n "rpc\.batch-request-limit" builder packaging docs
   • Result: matches found across updated template/example files.
3. Confirmed scope is limited to template/docs key rename via diff review.

Additional comments

No runtime code path or default value was changed in this PR; this is a template/docs correctness alignment fix to prevent silent misconfiguration.

[claude]

Claude Code Review

This pull request is from a fork — automated review is disabled. A repository maintainer can comment @claude review to run a one-time review.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 52.33%. Comparing base (05ff6f4) to head (19c9705).
⚠️ Report is 3 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #2216      +/-   ##
===========================================
+ Coverage    52.30%   52.33%   +0.02%     
===========================================
  Files          885      885              
  Lines       155715   155715              
===========================================
+ Hits         81450    81489      +39     
+ Misses       69030    68998      -32     
+ Partials      5235     5228       -7     

see 15 files with indirect coverage changes
see 15 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[pratikspatil024]

Thank you!
Can you update the default value to 1000? Also make sure to run make docs.

[pratikspatil024]

Thanks @odupontt - is it possible for you to sign this commit? You can rebase locally to rewrite history with signed commits and force-push.
If not, I can do it from my end.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[odupontt]

Thanks @odupontt - is it possible for you to sign this commit? You can rebase locally to rewrite history with signed commits and force-push. If not, I can do it from my end.

Hi @pratikspatil024 - Done, I rebased and force-pushed the branch with signed commits; the latest commit (c9bfba0) is now Verified.

[pratikspatil024]

Thanks @odupontt - did you also run make docs?

[odupontt]

Thanks @odupontt - did you also run make docs?

@pratikspatil024 yes, I ran make docs and it produced no changes.