Use bollard crate directly, upgrade serde to 1.0.152

[banool]

Description

This PR changes us from using my Bollard fork that uses an older serde_with version to using the main Bollard crate.

Recently I landed a PR to serde_with that changed the minimum required serde version from 1.0.157 to 1.0.152: jonasbb/serde_with#653. Bollard uses serde_with, so now the transitive dependency on serde through serde_with from Bollard is no longer 1.0.157 but 1.0.152, which we can use happily without breaking the the analyze formats code (see this issue for more details: #10424).

Test Plan

cargo run -p generate-format -- --corpus aptos

[github-actions]

✅ Forge suite compat success on aptos-node-v1.6.2 ==> 6e4f5abf619fe178bd0538bb4ab57e55ceb35072

Compatibility test results for aptos-node-v1.6.2 ==> 6e4f5abf619fe178bd0538bb4ab57e55ceb35072 (PR)
1. Check liveness of validators at old version: aptos-node-v1.6.2
compatibility::simple-validator-upgrade::liveness-check : committed: 3017 txn/s, latency: 7230 ms, (p50: 7800 ms, p90: 9600 ms, p99: 11100 ms), latency samples: 165980
2. Upgrading first Validator to new version: 6e4f5abf619fe178bd0538bb4ab57e55ceb35072
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 1827 txn/s, latency: 15914 ms, (p50: 18700 ms, p90: 22300 ms, p99: 22500 ms), latency samples: 93200
3. Upgrading rest of first batch to new version: 6e4f5abf619fe178bd0538bb4ab57e55ceb35072
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 1324 txn/s, latency: 16446 ms, (p50: 19000 ms, p90: 22000 ms, p99: 25600 ms), latency samples: 92700
4. upgrading second batch to new version: 6e4f5abf619fe178bd0538bb4ab57e55ceb35072
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 3454 txn/s, latency: 9074 ms, (p50: 9700 ms, p90: 12400 ms, p99: 12900 ms), latency samples: 145100
5. check swarm health
Compatibility test for aptos-node-v1.6.2 ==> 6e4f5abf619fe178bd0538bb4ab57e55ceb35072 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 6e4f5abf619fe178bd0538bb4ab57e55ceb35072

two traffics test: inner traffic : committed: 7818 txn/s, latency: 5015 ms, (p50: 4600 ms, p90: 5700 ms, p99: 22900 ms), latency samples: 3377440
two traffics test : committed: 100 txn/s, latency: 2578 ms, (p50: 2200 ms, p90: 2700 ms, p99: 12300 ms), latency samples: 1860
Latency breakdown for phase 0: ["QsBatchToPos: max: 0.213, avg: 0.199", "QsPosToProposal: max: 0.435, avg: 0.186", "ConsensusProposalToOrdered: max: 0.622, avg: 0.588", "ConsensusOrderedToCommit: max: 0.594, avg: 0.552", "ConsensusProposalToCommit: max: 1.208, avg: 1.140"]
Max round gap was 1 [limit 4] at version 1703872. Max no progress secs was 4.525475 [limit 10] at version 1703872.
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.5.1 ==> 6e4f5abf619fe178bd0538bb4ab57e55ceb35072

Compatibility test results for aptos-node-v1.5.1 ==> 6e4f5abf619fe178bd0538bb4ab57e55ceb35072 (PR)
Upgrade the nodes to version: 6e4f5abf619fe178bd0538bb4ab57e55ceb35072
framework_upgrade::framework-upgrade::full-framework-upgrade : committed: 4145 txn/s, latency: 4969 ms, (p50: 4800 ms, p90: 8100 ms, p99: 8700 ms), latency samples: 236320
5. check swarm health
Compatibility test for aptos-node-v1.5.1 ==> 6e4f5abf619fe178bd0538bb4ab57e55ceb35072 passed
Test Ok

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