Finish Aptos local CRE read/write parity

[cawthorne]

Supersedes #21610 for CI purposes.

This branch is a clean, signed squash of the current #21610 tree onto latest develop. The code/content is intentionally the same as the current PR head; the goal is to rerun CI on a fresh branch and PR without the old churn/merge history.

Notable behavior kept:

• topology-driven LocalOnly = don.HasOnlyLocalCapabilities()
• capability-registration UseCapRegOCRConfig = false
• chainlink-common remains on main
• no remote-exposure / launcher patch in this PR

Local verification on the squashed tree:

• Aptos local CRE read smoke passes
• write capability setup is present, but write smoke does not run by default

If CI is clean here, we can use this PR as the merge candidate and close #21610.

[github-actions]

CORA - Pending Reviewers

Codeowners Entry	Overall	Num Files	Owners
*	⏳	51	@smartcontractkit/foundations, @smartcontractkit/core
/core/capabilities/	⏳	3	@smartcontractkit/keystone, @smartcontractkit/capabilities-team
/core/services/standardcapabilities	⏳	2	@smartcontractkit/keystone
/integration-tests/**/*ccip*	⏳	1	@smartcontractkit/ccip-offchain, @smartcontractkit/core, @smartcontractkit/ccip
/deployment/cre	⏳	10	@smartcontractkit/keystone, @smartcontractkit/operations-platform
/.github/**	⏳	1	@smartcontractkit/devex-cicd, @smartcontractkit/devex-tooling, @smartcontractkit/core
go.md	⏳	1	@smartcontractkit/core, @smartcontractkit/foundations
go.mod	⏳	9	@smartcontractkit/core, @smartcontractkit/foundations
go.sum	⏳	9	@smartcontractkit/core, @smartcontractkit/foundations
integration-tests/go.mod	⏳	1	@smartcontractkit/core, @smartcontractkit/devex-tooling, @smartcontractkit/foundations
integration-tests/go.sum	⏳	1	@smartcontractkit/core, @smartcontractkit/devex-tooling, @smartcontractkit/foundations

Legend: ✅ Approved | ❌ Changes Requested | 💬 Commented | 🚫 Dismissed | ⏳ Pending | ❓ Unknown

For more details, see the full review summary.

[github-actions]

I see you updated files related to core. Please run make gocs in the root directory to add a changeset as well as in the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

[github-actions]

✅ No conflicts with other open PRs targeting develop

[trunk-io]

     

View Full Report ↗︎ ⋅ Docs

[cl-sonarqube-production]

Quality Gate passed

Issues
13 New issues
11 Fixed issues
0 Accepted issues

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

See analysis details on SonarQube