feat: deploy custom topology mcms [CLD-2766]

[ecPablo]

To be merged after: #99
Implements the deploy custom topology changeset and sequences for EVM which allows users to deploy custom mcms / timelock structures without custom coding topologies.

AI Summary

This pull request refactors the EVM operations code in the MCMS legacy changesets by consolidating and updating imports to use a newer, centralized evm/operations package. The changes primarily involve replacing references to the old oputil and legacy operation types with the new evmops types and functions, improving maintainability and consistency across the codebase. No functional logic is altered; this is a structural cleanup.

Refactoring and Codebase Cleanup:

• Replaced all imports of oputil and legacy operation types in multiple files (such as deploy_mcms_with_timelock.go, grant_timelock.go, and various operation and sequence files) with the new evmops package from mcms/evm/operations for EVM operation utilities and types. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

• Updated all usages of EVM operation constructors and types (e.g., NewEVMDeployOperation, NewEVMCallOperation, EVMDeployInput, RetryDeploymentWithGasBoost, EVMCallOutput, etc.) to use the new evmops equivalents, ensuring type compatibility and consistency. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16]

• Adjusted function signatures and return types throughout the EVM operation and sequence logic to use the new types from evmops, removing all direct dependencies on the deprecated oputil package. [1] [2] [3] [4] [5] [6]

This update is a non-functional, structural refactor that will make future maintenance and enhancements easier by consolidating EVM operation logic in a single, modern package.

[github-actions]

Release impact (release-please)

Current version	0.7.1 (on main)
After merge	0.8.0 (minor bump)

PR title: feat: deploy custom topology mcms [CLD-2766]

Merging this PR as-is will contribute a minor bump to the next release-please release PR.

Conventional commit → bump

Intent	PR title prefix	Bump
Bug fix	fix:	patch
New feature	feat:	minor
Breaking change	feat!: / fix!: or BREAKING CHANGE: / BREAKING-CHANGE: in description	major
No release	chore:, docs:, ci:, refactor:, etc.	none

Update the PR title before merge if you need a different bump (squash commit message = PR title).

Preview is based on this PR title only. The release-please release PR may include other unreleased commits already on main.

[graham-chainlink]

I think my force push in my ggoh/CLD-2762/transfer-to-mcms branch stuffed up your PR here, so changes are a bit hard to see now.

[graham-chainlink]

Looks reasonable to me!

[graham-chainlink]

i wonder should it deduplicate or just error, sounds like an user error that the user should know?

[ecPablo]

I feel deduplicate is a a bit better here, as we throwing an error would only mean they have to fix something that we can automatically fix for them. I added some comments documenting the decision here 6c772fd

[graham-chainlink]

i see, i was thinking this can only be an user error and they might want to have a different address but copied the same one accidentally, it could be a mistake that needs to be rectified instead of silently ignored if that make sense? What do you think?

[cl-sonarqube-production]

Quality Gate passed

Issues
4 New issues
0 Fixed issues
0 Accepted issues

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

See analysis details on SonarQube