Using MaxGasPrice from txRequest

[yashnevatia]

https://smartcontract-it.atlassian.net/browse/PLEX-1522
Depends on:
smartcontractkit/chainlink-protos#256
smartcontractkit/chainlink-common#1764
smartcontractkit/chainlink-framework#80
smartcontractkit/chainlink-evm#323

[github-actions]

👋 yashnevatia, 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!

[Copilot]

Pull request overview

This PR updates the EVM service to use the MaxGasPrice parameter from transaction requests when submitting transactions. This allows callers to specify a maximum gas price limit for their transactions, which is then passed through to the underlying transaction manager.

Changes:

• Updated dependency versions for chainlink-evm and chainlink-framework/chains packages
• Added logic to extract and use MaxGasPrice from transaction requests in the EVM service

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File	Description
go.mod	Updated chainlink-evm and chainlink-framework/chains dependencies to newer versions
core/services/relay/evm/evm_service.go	Added extraction and usage of MaxGasPrice from txRequest.GasConfig when submitting transactions

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

I see you updated files related to core. Please run pnpm changeset 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.

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed 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