[gha] cargo metadata uploader

[ibalajiarun]

Description

This PR introduces a new workflow that generate a cargo metadata json file and uploads it to a GCS bucket. The metadata will be used for target determinator CLI.

Test Plan

GHA checks runs fine.

[geekflyer]

you can do this kinda in 1 line without writing an intermediate file:

Suggested change

	gsutil cp ${METADATA_FILENAME} gs://aptos-core-cargo-metadata-public/${METADATA_FILENAME}
	cargo metadata --all-features | gsutil cp - gs://aptos-core-cargo-metadata-public/metadata-${{ github.sha }}.json

[github-actions]

✅ Forge suite compat success on aptos-node-v1.5.1 ==> 84e9e401e57276d1423ebbee541899bf143395a5

Compatibility test results for aptos-node-v1.5.1 ==> 84e9e401e57276d1423ebbee541899bf143395a5 (PR)
1. Check liveness of validators at old version: aptos-node-v1.5.1
compatibility::simple-validator-upgrade::liveness-check : committed: 4261 txn/s, latency: 6945 ms, (p50: 6700 ms, p90: 9300 ms, p99: 13500 ms), latency samples: 178980
2. Upgrading first Validator to new version: 84e9e401e57276d1423ebbee541899bf143395a5
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 1744 txn/s, latency: 15706 ms, (p50: 19200 ms, p90: 22000 ms, p99: 23100 ms), latency samples: 92440
3. Upgrading rest of first batch to new version: 84e9e401e57276d1423ebbee541899bf143395a5
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 1714 txn/s, latency: 16510 ms, (p50: 19200 ms, p90: 21900 ms, p99: 22600 ms), latency samples: 89140
4. upgrading second batch to new version: 84e9e401e57276d1423ebbee541899bf143395a5
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 2232 txn/s, latency: 9578 ms, (p50: 10000 ms, p90: 13300 ms, p99: 14400 ms), latency samples: 140620
5. check swarm health
Compatibility test for aptos-node-v1.5.1 ==> 84e9e401e57276d1423ebbee541899bf143395a5 passed
Test Ok

• Grafana dashboard
• Humio Logs
• Test runner output
• Test run is land-blocking

[github-actions]

✅ Forge suite framework_upgrade success on aptos-node-v1.5.1 ==> 84e9e401e57276d1423ebbee541899bf143395a5

Compatibility test results for aptos-node-v1.5.1 ==> 84e9e401e57276d1423ebbee541899bf143395a5 (PR)
Upgrade the nodes to version: 84e9e401e57276d1423ebbee541899bf143395a5
framework_upgrade::framework-upgrade::full-framework-upgrade : committed: 4649 txn/s, latency: 6984 ms, (p50: 7500 ms, p90: 9900 ms, p99: 11700 ms), latency samples: 172040
5. check swarm health
Compatibility test for aptos-node-v1.5.1 ==> 84e9e401e57276d1423ebbee541899bf143395a5 passed
Test Ok

• Grafana dashboard
• Humio Logs
• Test runner output
• Test run is land-blocking

[github-actions]

✅ Forge suite realistic_env_max_load success on 84e9e401e57276d1423ebbee541899bf143395a5

two traffics test: inner traffic : committed: 6738 txn/s, latency: 5809 ms, (p50: 5700 ms, p90: 7200 ms, p99: 10500 ms), latency samples: 2917980
two traffics test : committed: 100 txn/s, latency: 3027 ms, (p50: 2900 ms, p90: 3600 ms, p99: 5100 ms), latency samples: 1900
Max round gap was 1 [limit 4] at version 1356313. Max no progress secs was 3.530895 [limit 10] at version 1356313.
Test Ok

• Grafana dashboard
• Humio Logs
• Test runner output
• Test run is land-blocking