aptos-core [release-tooling] Fix release tooling for 1.2.0

Description

Cherrypick the fix from v.1.2.0 to main. The biggest change is to add an option for the framework release to force cli to compile the framework at a given bytecode version to avoid release framework at a newer unexpected bytecode version.

Original PR is #6248.

Test Plan

Updated the example config via

cargo run -p aptos-release-builder -- write-default --output-path aptos-move/aptos-release-builder/data/example.yaml

And generated the scripts via

cargo run -p aptos-release-builder -- generate-proposals --release-config aptos-move/aptos-release-builder/data/example.yaml --output-dir ~/release

And manually inspected the generated scripts to verify that the modules are indeed emitted at file format version 5.

Jan 26 '23 01:01 runtian-zhou

The next step here is to create an automated workflow for future framework release with this tool.

Jan 26 '23 02:01 runtian-zhou

We aren't tracking it right now. For this round we are creating the yaml file on the release branch. In the future tho, we should expect to have the yaml file to always reside in main branch so that when we perform the branch cut we can just create a new yaml on main.

Jan 26 '23 20:01 runtian-zhou

Forge is running suite `land_blocking` on `d26541de6b49dc24f75d66c064d143a5387d0dd8`

Jan 31 '23 23:01 github-actions[bot]

Forge is running suite `compat` on `testnet_2d8b1b57553d869190f61df1aaf7f31a8fc19a7b` ==> `d26541de6b49dc24f75d66c064d143a5387d0dd8`

Jan 31 '23 23:01 github-actions[bot]

:white_check_mark: Forge suite `land_blocking` success on `d26541de6b49dc24f75d66c064d143a5387d0dd8`

performance benchmark with full nodes : 5935 TPS, 6670 ms latency, 14500 ms p99 latency,(!) expired 1940 out of 2536220 txns
Test Ok

Jan 31 '23 23:01 github-actions[bot]

:white_check_mark: Forge suite `compat` success on `testnet_2d8b1b57553d869190f61df1aaf7f31a8fc19a7b` ==> `d26541de6b49dc24f75d66c064d143a5387d0dd8`

Compatibility test results for testnet_2d8b1b57553d869190f61df1aaf7f31a8fc19a7b ==> d26541de6b49dc24f75d66c064d143a5387d0dd8 (PR)
1. Check liveness of validators at old version: testnet_2d8b1b57553d869190f61df1aaf7f31a8fc19a7b
compatibility::simple-validator-upgrade::liveness-check : 7698 TPS, 4987 ms latency, 7500 ms p99 latency,no expired txns
2. Upgrading first Validator to new version: d26541de6b49dc24f75d66c064d143a5387d0dd8
compatibility::simple-validator-upgrade::single-validator-upgrade : 4765 TPS, 8352 ms latency, 10600 ms p99 latency,no expired txns
3. Upgrading rest of first batch to new version: d26541de6b49dc24f75d66c064d143a5387d0dd8
compatibility::simple-validator-upgrade::half-validator-upgrade : 5084 TPS, 7889 ms latency, 11100 ms p99 latency,no expired txns
4. upgrading second batch to new version: d26541de6b49dc24f75d66c064d143a5387d0dd8
compatibility::simple-validator-upgrade::rest-validator-upgrade : 6852 TPS, 5608 ms latency, 10000 ms p99 latency,no expired txns
5. check swarm health
Compatibility test for testnet_2d8b1b57553d869190f61df1aaf7f31a8fc19a7b ==> d26541de6b49dc24f75d66c064d143a5387d0dd8 passed
Test Ok

Jan 31 '23 23:01 github-actions[bot]

Forge is running suite `land_blocking` on `e90549938ddedc91497e34cfbd569731771bedfb`

Feb 01 '23 02:02 github-actions[bot]

Forge is running suite `compat` on `testnet_2d8b1b57553d869190f61df1aaf7f31a8fc19a7b` ==> `e90549938ddedc91497e34cfbd569731771bedfb`

Feb 01 '23 02:02 github-actions[bot]

:white_check_mark: Forge suite `compat` success on `testnet_2d8b1b57553d869190f61df1aaf7f31a8fc19a7b` ==> `e90549938ddedc91497e34cfbd569731771bedfb`

Compatibility test results for testnet_2d8b1b57553d869190f61df1aaf7f31a8fc19a7b ==> e90549938ddedc91497e34cfbd569731771bedfb (PR)
1. Check liveness of validators at old version: testnet_2d8b1b57553d869190f61df1aaf7f31a8fc19a7b
compatibility::simple-validator-upgrade::liveness-check : 8011 TPS, 5002 ms latency, 7800 ms p99 latency,no expired txns
2. Upgrading first Validator to new version: e90549938ddedc91497e34cfbd569731771bedfb
compatibility::simple-validator-upgrade::single-validator-upgrade : 4526 TPS, 9021 ms latency, 11600 ms p99 latency,no expired txns
3. Upgrading rest of first batch to new version: e90549938ddedc91497e34cfbd569731771bedfb
compatibility::simple-validator-upgrade::half-validator-upgrade : 4664 TPS, 8540 ms latency, 11300 ms p99 latency,no expired txns
4. upgrading second batch to new version: e90549938ddedc91497e34cfbd569731771bedfb
compatibility::simple-validator-upgrade::rest-validator-upgrade : 7119 TPS, 5289 ms latency, 9100 ms p99 latency,no expired txns
5. check swarm health
Compatibility test for testnet_2d8b1b57553d869190f61df1aaf7f31a8fc19a7b ==> e90549938ddedc91497e34cfbd569731771bedfb passed
Test Ok

Feb 01 '23 03:02 github-actions[bot]

:white_check_mark: Forge suite `land_blocking` success on `e90549938ddedc91497e34cfbd569731771bedfb`

performance benchmark with full nodes : 6246 TPS, 6363 ms latency, 9800 ms p99 latency,no expired txns
Test Ok

Feb 01 '23 03:02 github-actions[bot]

Forge is running suite `compat` on `testnet_2d8b1b57553d869190f61df1aaf7f31a8fc19a7b` ==> `232f03ac71f59c588c856cb9aceb51f395818e11`

Feb 01 '23 19:02 github-actions[bot]

Forge is running suite `land_blocking` on `232f03ac71f59c588c856cb9aceb51f395818e11`

Feb 01 '23 19:02 github-actions[bot]

:white_check_mark: Forge suite `land_blocking` success on `232f03ac71f59c588c856cb9aceb51f395818e11`

performance benchmark with full nodes : 6195 TPS, 6410 ms latency, 10800 ms p99 latency,(!) expired 100 out of 2645380 txns
Test Ok

Feb 01 '23 19:02 github-actions[bot]