aptos-core feat: Batch Vote Func

Description

This PR adds batch voting functionalities for Aptos governance so voters can vote with multiple stake pools in a single transaction.

Type of Change

[x] 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
[x] Aptos Framework
[ ] Aptos CLI/SDK
[ ] Developer Infrastructure
[ ] Other (specify)

How Has This Been Tested?

Unit tests

Checklist

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

Apr 25 '24 07:04 canalgroup

⏱️ 28s total CI duration on this PR

Job	Cumulative Duration	Recent Runs
permission-check	9s	🟥 🟥
permission-check	8s	🟥 🟥
permission-check	6s	🟥 🟥
permission-check	5s	🟥 🟥

_{settings ⋅ feedback ⋅ docs ⋅ learn more about trunk.io}

Apr 25 '24 07:04 trunk-io[bot]

LGTM, overall! I left one comment about replacing partial_vote with vote_internal for consistency and efficiency.

If it fails for one stake_pool, the entire function call will fail. Is that fine, or do we want to forgive those failures of some individual stake pools? (@movekevin )

It's not possible since there's no try catch anyway

May 30 '24 18:05 movekevin

Forge is running suite `framework_upgrade` on `a68e71c05caebf01504d4499110f3fba213fb53d` ==> `63ee8e4b35e31de3369416ea0ea8d05e9591f2dd`

May 30 '24 18:05 github-actions[bot]

Forge is running suite `compat` on `a68e71c05caebf01504d4499110f3fba213fb53d` ==> `63ee8e4b35e31de3369416ea0ea8d05e9591f2dd`

May 30 '24 18:05 github-actions[bot]

Forge is running suite `realistic_env_max_load` on `63ee8e4b35e31de3369416ea0ea8d05e9591f2dd`

May 30 '24 18:05 github-actions[bot]

:white_check_mark: Forge suite `compat` success on `a68e71c05caebf01504d4499110f3fba213fb53d` ==> `63ee8e4b35e31de3369416ea0ea8d05e9591f2dd`

Compatibility test results for a68e71c05caebf01504d4499110f3fba213fb53d ==> 63ee8e4b35e31de3369416ea0ea8d05e9591f2dd (PR)
1. Check liveness of validators at old version: a68e71c05caebf01504d4499110f3fba213fb53d
compatibility::simple-validator-upgrade::liveness-check : committed: 8321.674675563565 txn/s, latency: 3377.0537244693633 ms, (p50: 2700 ms, p90: 4100 ms, p99: 23200 ms), latency samples: 349580
2. Upgrading first Validator to new version: 63ee8e4b35e31de3369416ea0ea8d05e9591f2dd
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 2136.162657504432 txn/s, latency: 14175.273824561404 ms, (p50: 13600 ms, p90: 23000 ms, p99: 24600 ms), latency samples: 85500
3. Upgrading rest of first batch to new version: 63ee8e4b35e31de3369416ea0ea8d05e9591f2dd
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 3342.1479848104777 txn/s, latency: 9225.05058722429 ms, (p50: 9100 ms, p90: 13900 ms, p99: 14200 ms), latency samples: 139640
4. upgrading second batch to new version: 63ee8e4b35e31de3369416ea0ea8d05e9591f2dd
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 6390.698264750706 txn/s, latency: 5082.49396660764 ms, (p50: 4800 ms, p90: 8500 ms, p99: 9600 ms), latency samples: 237180
5. check swarm health
Compatibility test for a68e71c05caebf01504d4499110f3fba213fb53d ==> 63ee8e4b35e31de3369416ea0ea8d05e9591f2dd passed
Test Ok

May 30 '24 18:05 github-actions[bot]

:white_check_mark: Forge suite `realistic_env_max_load` success on `63ee8e4b35e31de3369416ea0ea8d05e9591f2dd`

two traffics test: inner traffic : committed: 8442.21416762154 txn/s, latency: 4646.3687302397575 ms, (p50: 4500 ms, p90: 5400 ms, p99: 10200 ms), latency samples: 3643680
two traffics test : committed: 99.97802620770126 txn/s, latency: 1871.788953488372 ms, (p50: 1800 ms, p90: 2100 ms, p99: 2400 ms), latency samples: 1720
Latency breakdown for phase 0: ["QsBatchToPos: max: 0.219, avg: 0.208", "QsPosToProposal: max: 0.213, avg: 0.199", "ConsensusProposalToOrdered: max: 0.424, avg: 0.404", "ConsensusOrderedToCommit: max: 0.398, avg: 0.389", "ConsensusProposalToCommit: max: 0.803, avg: 0.793"]
Max round gap was 1 [limit 4] at version 1834062. Max no progress secs was 4.951443 [limit 15] at version 1834062.
Test Ok

May 30 '24 18:05 github-actions[bot]