Bump chainlink-evm to include per-OFA gas limit + svr v1.3.0

[mostlyconsistent]

What

Bumps chainlink-evm to v0.3.4-0.20260716150153-cd1826496e2d to include smartcontractkit/chainlink-evm#503 - emit per-OFA gas limit and bump chainlink-protos/svr to v1.3.0.

Mechanical dependency bump across all modules (make tidy); svr moves to v1.3.0 as an indirect dependency only, no core code changes.

Requires

• Bump chainlink-protos/svr to v1.3.0 and emit per-OFA gas limit chainlink-evm#503

[github-actions]

👋 mostlyconsistent, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

[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]

     

Failed Test	Failure Summary	Logs
Test_CCIPTokenTransfer_Sui2EVM_LockReleaseTokenPool_Revert	The test failed due to an unspecified error during execution, with no clear indication of what caused the failure.	Logs ↗︎
TestIntegration_MercuryV3	The test failed without a specific error message, indicating an unspecified failure during the integration test.	Logs ↗︎
TestIntegration_MercuryV2	The test failed due to an unspecified error during execution, with no specific failure message provided.	Logs ↗︎
TestIntegration_MercuryV2/receives_at_least_one_report_per_feed_from_each_oracle_when_EAs_are_at_80%_reliability	The test failed during the integration test for MercuryV2, specifically when checking report reception from oracles at 80% reliability.	Logs ↗︎

... and 1 more

View Full Report ↗︎ ⋅ Docs

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube