[Worm CLI] Implement testing for worm submit command (ContractUpgrade case)

[AlberErre]

Hi everyone 👋!

Would be nice to have some test coverage for the most important Worm CLI commands ⚙️. I've been able to discuss this internally with the core team, and looks like a good approach would be to start testing the worm submit command, specifically the ContractUpgrade case.

The main goal for this test suite would be to secure this command's functionality. This way we could ensure this command is still functional after any refactor done on the CLI.

As these commands interacts directly with several blockchains networks, end-to-end testing would be messy to implement and expensive to execute in this case. Instead, I propose a unit-testing approach.

ℹ️ This unit-testing approach would focus on capturing network calls and verify they are as expected.

At the end of the day, worm submit command launches REST API calls. These API calls could be against a Solana endpoint to submit a transaction, or another chains (such as Ethereum). We could use tools such as mswjs to capture these REST API request. Therefore they will never reach the network on the test environment. Instead, they are captured and we can match if these request are as we expected.

Thoughts? 👀

[heyitaki]

I agree with this approach, it's outside of the scope of these tests to ensure external factors like node uptime.

[AlberErre]

A Pull request has been created to cover these test cases 🎉
The PR is available here -> #3229