[Aptos Data Client] Enable v2 requests.

[JoshLind]

Description

How Has This Been Tested?

Key Areas to Review

Type of Change

• New feature
• Bug fix
• Breaking change
• Performance improvement
• Refactoring
• Dependency update
• Documentation update
• Tests

Which Components or Systems Does This Change Impact?

• Validator Node
• Full Node (API, Indexer, etc.)
• Move/Aptos Virtual Machine
• Aptos Framework
• Aptos CLI/SDK
• Developer Infrastructure
• Move Compiler
• Other (specify)

Checklist

• I have read and followed the CONTRIBUTING doc
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I identified and added all stakeholders and component owners affected by this change as reviewers
• I tested both happy and unhappy path of the functionality
• I have made corresponding changes to the documentation

[github-actions]

✅ Forge suite compat success on 0717b6e75eafda270a60b54c43a1874b74662c9c ==> c7b77f51e2218d0f919dfe4c4654f33c214fbb2e

Compatibility test results for 0717b6e75eafda270a60b54c43a1874b74662c9c ==> c7b77f51e2218d0f919dfe4c4654f33c214fbb2e (PR)
1. Check liveness of validators at old version: 0717b6e75eafda270a60b54c43a1874b74662c9c
compatibility::simple-validator-upgrade::liveness-check : committed: 6367.02 txn/s, latency: 4950.61 ms, (p50: 3700 ms, p70: 4400, p90: 12300 ms, p99: 13600 ms), latency samples: 211600
2. Upgrading first Validator to new version: c7b77f51e2218d0f919dfe4c4654f33c214fbb2e
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 2448.65 txn/s, latency: 13801.52 ms, (p50: 15200 ms, p70: 15800, p90: 16200 ms, p99: 16200 ms), latency samples: 92560
3. Upgrading rest of first batch to new version: c7b77f51e2218d0f919dfe4c4654f33c214fbb2e
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 2477.22 txn/s, latency: 13621.35 ms, (p50: 15000 ms, p70: 15500, p90: 15900 ms, p99: 16100 ms), latency samples: 93380
4. upgrading second batch to new version: c7b77f51e2218d0f919dfe4c4654f33c214fbb2e
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 4343.34 txn/s, latency: 7801.69 ms, (p50: 8700 ms, p70: 9000, p90: 9200 ms, p99: 9400 ms), latency samples: 153880
5. check swarm health
Compatibility test for 0717b6e75eafda270a60b54c43a1874b74662c9c ==> c7b77f51e2218d0f919dfe4c4654f33c214fbb2e passed
Test Ok

• Grafana dashboard
• Humio Logs
• Axiom Logs
• Validator CPU Profile
• Fullnode CPU Profile
• Test runner output
• Test run is land-blocking

[github-actions]

✅ Forge suite realistic_env_max_load success on c7b77f51e2218d0f919dfe4c4654f33c214fbb2e

two traffics test: inner traffic : committed: 11135.21 txn/s, latency: 3381.05 ms, (p50: 3300 ms, p70: 3300, p90: 3900 ms, p99: 4800 ms), latency samples: 4233920
two traffics test : committed: 100.00 txn/s, latency: 1117.70 ms, (p50: 900 ms, p70: 1000, p90: 1200 ms, p99: 7100 ms), latency samples: 1700
Latency breakdown for phase 0: ["MempoolToBlockCreation: max: 2.721, avg: 2.465", "ConsensusProposalToOrdered: max: 0.168, avg: 0.164", "ConsensusOrderedToCommit: max: 0.248, avg: 0.218", "ConsensusProposalToCommit: max: 0.410, avg: 0.382"]
Max non-epoch-change gap was: 0 rounds at version 0 (avg 0.00) [limit 4], 0.89s no progress at version 2790190 (avg 0.07s) [limit 15].
Max epoch-change gap was: 0 rounds at version 0 (avg 0.00) [limit 4], 0.39s no progress at version 4594325 (avg 0.35s) [limit 16].
Test Ok

• Grafana dashboard
• Humio Logs
• Axiom Logs
• Validator CPU Profile
• Fullnode CPU Profile
• Test runner output
• Test run is land-blocking