[gha] label to trigger forge e2e perf test only

[ibalajiarun]

Description

When we are debugging a PR, we mostly want only the forge e2e test to run, so this PR introduces a new GH PR label to run just that test and defer the compat and framework upgrade tests.

Test Plan

[github-actions]

✅ Forge suite compat success on aptos-node-v1.7.2 ==> a887c415b682e2de006696cb325a0cfa8aa57e3b

Compatibility test results for aptos-node-v1.7.2 ==> a887c415b682e2de006696cb325a0cfa8aa57e3b (PR)
1. Check liveness of validators at old version: aptos-node-v1.7.2
compatibility::simple-validator-upgrade::liveness-check : committed: 4370 txn/s, latency: 6880 ms, (p50: 5400 ms, p90: 10200 ms, p99: 29900 ms), latency samples: 174820
2. Upgrading first Validator to new version: a887c415b682e2de006696cb325a0cfa8aa57e3b
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 1844 txn/s, latency: 15666 ms, (p50: 18500 ms, p90: 22200 ms, p99: 22600 ms), latency samples: 92200
3. Upgrading rest of first batch to new version: a887c415b682e2de006696cb325a0cfa8aa57e3b
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 1842 txn/s, latency: 15570 ms, (p50: 19500 ms, p90: 22000 ms, p99: 22300 ms), latency samples: 92100
4. upgrading second batch to new version: a887c415b682e2de006696cb325a0cfa8aa57e3b
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 3568 txn/s, latency: 8817 ms, (p50: 9600 ms, p90: 12600 ms, p99: 12800 ms), latency samples: 146320
5. check swarm health
Compatibility test for aptos-node-v1.7.2 ==> a887c415b682e2de006696cb325a0cfa8aa57e3b passed
Test Ok

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

[github-actions]

✅ Forge suite realistic_env_max_load success on a887c415b682e2de006696cb325a0cfa8aa57e3b

two traffics test: inner traffic : committed: 8695 txn/s, latency: 4520 ms, (p50: 4200 ms, p90: 5100 ms, p99: 10500 ms), latency samples: 3747900
two traffics test : committed: 100 txn/s, latency: 2222 ms, (p50: 2100 ms, p90: 2700 ms, p99: 5800 ms), latency samples: 1780
Latency breakdown for phase 0: ["QsBatchToPos: max: 0.210, avg: 0.198", "QsPosToProposal: max: 0.156, avg: 0.136", "ConsensusProposalToOrdered: max: 0.599, avg: 0.579", "ConsensusOrderedToCommit: max: 0.502, avg: 0.480", "ConsensusProposalToCommit: max: 1.085, avg: 1.059"]
Max round gap was 1 [limit 4] at version 1990148. Max no progress secs was 4.404907 [limit 10] at version 1990148.
Test Ok

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

[github-actions]

✅ Forge suite framework_upgrade success on aptos-node-v1.7.2 ==> a887c415b682e2de006696cb325a0cfa8aa57e3b

Compatibility test results for aptos-node-v1.7.2 ==> a887c415b682e2de006696cb325a0cfa8aa57e3b (PR)
Upgrade the nodes to version: a887c415b682e2de006696cb325a0cfa8aa57e3b
framework_upgrade::framework-upgrade::full-framework-upgrade : committed: 6972 txn/s, latency: 4827 ms, (p50: 4800 ms, p90: 7800 ms, p99: 8400 ms), latency samples: 244020
5. check swarm health
Compatibility test for aptos-node-v1.7.2 ==> a887c415b682e2de006696cb325a0cfa8aa57e3b passed
Test Ok

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