[SEV] Add a test to detect that CLI has become incompatible with framework (e.g. compilation errors) from the supported (see first point) branches.

[lbmeiyi]

before it is implemented, we need to test them manually and better communication

Action item from https://aptoslabs.pagerduty.com/incidents/Q09ZMX1SM4MJWT CLI 1.0.14 compilation was broken

[banool]

Asking here: https://aptos-org.slack.com/archives/C036X27DZNG/p1694010072277529.

[banool]

Alright so we want to uphold the following invariant:

Compiling and publishing with the latest Aptos CLI should work when you are using the framework from the following branches with their corresponding networks:

• devnet
• testnet
• mainnet

As in, publishing to devnet with a Move.toml where rev = "devnet" should work:

[dependencies]
AptosFramework = { git = "https://github.com/aptos-labs/aptos-core.git", subdir = "aptos-move/framework/aptos-framework/", rev = devnet }

It so happens we already test for that:

• https://github.com/aptos-labs/aptos-core/blob/07395aafcc170601fcb2641989a93228f78daa9b/crates/aptos/e2e/cases/move.py#L12
• https://github.com/aptos-labs/aptos-core/blob/af67b21a40d1b5cc6f60b27cc60199e169b27c85/.github/workflows/cli-e2e-tests.yaml#L22

So all we need to do is:

• Add something to the docs site.
• Perhaps emit a warning when the user uses a rev that isn't any of the above 3.

[0xmigo]

Add something to the docs site.

@banool Wanted to make sure. Which doc site are we referring to here?

[banool]

Whichever part of the docs talks about setting dependencies in Move packages (assuming we have such a section in the first place hahah).