Bump EVM and introduce Meter()

[mostlyconsistent]

What

Bumps chainlink-evm from v0.3.4-0.20260810110946-8174b6bb7fc9 to v0.3.4-0.20260914143713-424babc506ab and passes the global beholder meter into in-process chain construction:

Meter: beholder.GetMeter(),   

That is the only functional change here. It lets each EVM chain register the new evm_chain_config_info gauge (smartcontractkit/chainlink-evm#548) against the beholder client initGlobals has already set up, matching what the chainlink-evm LOOP plugin entrypoint already does.

Everything else is fallout from the bump:

• Automation/Keepers are gone from the EVM config schema (Remove automation chainlink-evm#545). [EVM.OCR2.Automation].GasLimit and EVM.GasEstimator.LimitJobType.Keeper no longer exist, so the fixtures and generated docs drop those keys: testdata/scripts/node/validate/*.txtar, core/services/chainlink/testdata/*,core/web/resolver/testdata/*, core/config/docs/chains-evm.toml, docs/CONFIG.md.
• chainlink-automation v0.8.1 falls out of the module graph as a result that's the go.md change.
• Mechanical go.mod/go.sum bump across all modules (make tidy).
• plugins/plugins.public.yaml gitRef bumped to track go.mod, which tools/plugout enforces.

Requires

• OEV-1648 Emit whitelisted EVM chain config metric chainlink-evm#548
• Remove automation chainlink-evm#545

[github-actions]

✅ No conflicts with other open PRs targeting develop

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

[trunk-io]

   

Failed Test	Failure Summary	Logs
Test_CCIP_RegulatedTokenTransfer_Aptos2EVM	The test failed due to an issue with the Aptos node API port configuration or container setup.	Logs ↗︎

View Full Report ↗︎ ⋅ Docs

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
4 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube