feat: test core_resources_rotation

[0xmovses]

Pull Request Overview

This PR adds testing infrastructure for core resources rotation functionality in the Movement framework. It includes a new test release module that reuses the pre-l1-merge commit with rotated core-resource-account settings and adds an end-to-end test for core resources rotation.

• Created a new framework release module for testing core resources rotation
• Added process composition configuration for the test environment
• Integrated a new e2e test binary for core resources rotation

Changelog

File	Description
protocol-units/execution/maptos/framework/releases/core-resources-rotation/src/lib.rs	Main library file defining the pre-l1-merge release configuration for rotation testing
protocol-units/execution/maptos/framework/releases/core-resources-rotation/src/cached.rs	Cached release implementation with gas upgrades, script modules, and feature flags
protocol-units/execution/maptos/framework/releases/core-resources-rotation/Cargo.toml	Package configuration and dependencies for the core resources rotation test module
process-compose/movement-full-node/process-compose.test-core-resources-rotation.yml	Process composition configuration for running the core resources rotation test

Testing

1. Test core_resources account rotation.

just movement-full-node native build.setup.eth-local.test-core-resources-rotation --keep-tui

2. Test governance signing after core_resource rotation:
   IMPORTANT
   Remember to rm -rf .movement/ before each run. Otherwise you'll get errors.

just movement-full-node native build.setup.eth-local.test-upgrade-framework-rotated-key --keep-tui

Notes

• More thorough checks can be done on core_resources capabilities if we want after this PR
• I'm aware that there is some code repetition in this PR. I did attempt to make the core_resource rotation a utility that could be shared across the repo but ran into lots of circular dependency issues, figured this isn't worth the time to solve as this repo will be essentially archived soon anyway. Repetition is fine.

[Copilot]

Pull Request Overview

This PR adds comprehensive testing infrastructure for core resources rotation functionality in the Movement framework. It introduces a new test module that reuses the pre-l1-merge commit configuration with rotated core-resource-account settings and provides end-to-end testing capabilities.

• Created a dedicated framework release module for testing core resources rotation
• Added process composition configuration files for different test scenarios
• Integrated new e2e test binaries for core resources rotation testing

Reviewed Changes

Copilot reviewed 8 out of 12 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
protocol-units/execution/maptos/framework/releases/pre-l1-merge/Cargo.toml	Updated package description for clarity
protocol-units/execution/maptos/framework/releases/core-resources-rotation/src/lib.rs	Main library defining pre-l1-merge release configuration for rotation testing
protocol-units/execution/maptos/framework/releases/core-resources-rotation/src/cached.rs	Cached release implementation with gas upgrades, script modules, and feature flags
protocol-units/execution/maptos/framework/releases/core-resources-rotation/build.rs	Build script for framework release generation
protocol-units/execution/maptos/framework/releases/core-resources-rotation/Cargo.toml	Package configuration and dependencies for the test module
process-compose/movement-full-node/process-compose.test-upgrade-framework-rotated-key.yml	Process composition for framework upgrade with rotated keys
process-compose/movement-full-node/process-compose.test-core-resources-rotation.yml	Process composition for core resources rotation testing
networks/movement/movement-client/Cargo.toml	Added new e2e test binary for core resources rotation

Comments suppressed due to low confidence (1)

protocol-units/execution/maptos/framework/releases/core-resources-rotation/build.rs:5

• The struct name BiarritzRc1 is inconsistent with the PreL1Merge struct used in lib.rs. Consider using consistent naming across the module.

	BiarritzRc1,                                         // Struct name

[0xmovses]

Some notes on this PR. I've found that after rotating the keys (successfully) for the core_resources account it is unable to sign off on the proposal, the VM reverts with EXCEEDED_MAX_TRANSACTION_SIZE Error. However, When sign the same governance proposal with an unrotated core_resources account, it passes. So I'm led to believed the VM error is reverting with that error but the error is some other reason. I've spent a lot of time trying to figure out why, but with no luck.

My Conclusion Is

It is not safe to rotate the core_resource signer and then attempt to sign off on governance proposasl with the rotated core_resource account.

I propose that

We use the current account to proceed with all the framework signing and do not rotate this key.

If anyone is curious the code for the test and the cmds to run those tests are all in the PR description above.