Docs(contract-addresses): update BondingManager target address

[SidestreamSweatyPumpkin]

Description

Updates the BondingManager contract address references to reflect the latest deployment on Arbitrum Mainnet. The previous target address is now documented as V12, and the current active target address has been updated in documentation version V2.

Scope

Validation

Follow-up Tasks

Type of Change

• Bug fix (fixes an issue)
• New content (adds new documentation)
• Content update (improves existing content)
• Style/formatting fix
• Information architecture change
• Other (please describe)

Related Issues

Fixes #
Related to #

Changes Made

• Updates the BondingManager (Target) address to reflect the latest protocol update on Arbitrum Mainnet.
• Fixes V11 BondingManager entry in the "Historical-deprecated" section in v2/resources/references/contract-addresses.mdx by updating it from 0x4bA7E7531Ab56bC8d78dB4FDc88D21F621f34BB4 to 0xF62C30242fccd3a46721f155d4d367De3fD5B3b3 pointing to the correct V11 address.
• Added V12 BondingManager entry in the "Historical-deprecated" section in v2/resources/references/contract-addresses.mdx documenting the previous target address 0x4bA7E7531Ab56bC8d78dB4FDc88D21F621f34BB4

Testing

• Tested locally with npm run dev
• Verified all links work
• Checked formatting and style
• Reviewed against style guides
• Screenshots (if UI changes)

Screenshots (if applicable)

s1:

s2:

Checklist

• My changes follow the style guides
• I've reviewed the Component Library for available components
• I've updated related pages if needed
• I've checked for broken links
• My changes are clear and easy to understand
• I've tested locally
• I've added/updated keywords and metadata if needed

Additional Notes

1. We opened this PR against the doc-v2 branch, as this was discussed in a previous PR.
2. We couldn’t update the V1 addresses because a commit hook prevents changes to the V1 documentation.

3. We noticed that the "Historical" section in the v2 docs lists active BondingManager marked as (current). In our opinion, this is incorrect, so we only added the new address on top, while adding previously active v11 and v12 addresses to the Historical section.
4. We found that contract address references exist in multiple files, including:

   • docs/resources/references/contract-addresses.mdx

   • v2/gateways/x-archived/references/contract-addresses.mdx

   • v2/gateways/resources/technical/dep-contract-addresses.mdx

   • v2/gateways/resources/technical/contract-addresses.mdx

   • v2/gateways/resources/technical/new-contract-addresses.mdx

   • v2/gateways/guides/monitoring-and-tooling/x-resources/v2-refs--contract-addresses.mdx

   • Currently, we have not updated the addresses in any of these files, since the purpose of each file is unclear, let us know if we need to update anything else or take over this task.

[DeveloperAlly]

Hello, these have been updated and contract updating has been moved to an automated pipeline (with blockchain verification checks) in Github Actions.

The updated v2/about/protocol/blockchain-contracts page and the contract-addresses pages found on about, gateways and orchestrators are also updated and use this Action now.

No more manual updates should be required! Ever 🎉

I will keep this PR open for a couple of days in case you have further comments - then close :)

Thanks!