[Rust][SDK] update rust sdk doc

[0xmigo]

Description

Test Plan

[xbtmatt]

How come we're having them apply the patch as opposed to us doing it directly to the SDK? Just trying to understand- not sure I do

[0xmigo]

How come we're having them apply the patch as opposed to us doing it directly to the SDK? Just trying to understand- not sure I do

@xbtmatt Good question! Greg and I was looking at the rust doc, and we found this - https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html

Remember that [patch] is applicable transitively but can only be defined at the top level so we consumers of my-library have to repeat the [patch] section if necessary.

[github-actions]

✅ Forge suite compat success on aptos-node-v1.5.1 ==> 71c655a6680ed765c398e5e7d753b58571381d5a

Compatibility test results for aptos-node-v1.5.1 ==> 71c655a6680ed765c398e5e7d753b58571381d5a (PR)
1. Check liveness of validators at old version: aptos-node-v1.5.1
compatibility::simple-validator-upgrade::liveness-check : committed: 4414 txn/s, latency: 6764 ms, (p50: 6300 ms, p90: 9200 ms, p99: 18400 ms), latency samples: 176560
2. Upgrading first Validator to new version: 71c655a6680ed765c398e5e7d753b58571381d5a
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 1786 txn/s, latency: 16342 ms, (p50: 18700 ms, p90: 22300 ms, p99: 22600 ms), latency samples: 92900
3. Upgrading rest of first batch to new version: 71c655a6680ed765c398e5e7d753b58571381d5a
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 1850 txn/s, latency: 15676 ms, (p50: 18500 ms, p90: 22000 ms, p99: 22300 ms), latency samples: 92540
4. upgrading second batch to new version: 71c655a6680ed765c398e5e7d753b58571381d5a
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 3296 txn/s, latency: 9716 ms, (p50: 9900 ms, p90: 13800 ms, p99: 14300 ms), latency samples: 141740
5. check swarm health
Compatibility test for aptos-node-v1.5.1 ==> 71c655a6680ed765c398e5e7d753b58571381d5a 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 71c655a6680ed765c398e5e7d753b58571381d5a

two traffics test: inner traffic : committed: 6852 txn/s, latency: 5726 ms, (p50: 5400 ms, p90: 7200 ms, p99: 10800 ms), latency samples: 2960400
two traffics test : committed: 100 txn/s, latency: 3134 ms, (p50: 3100 ms, p90: 3700 ms, p99: 4500 ms), latency samples: 1880
Max round gap was 1 [limit 4] at version 1486085. Max no progress secs was 3.748802 [limit 10] at version 1486085.
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 ==> 71c655a6680ed765c398e5e7d753b58571381d5a

Compatibility test results for aptos-node-v1.5.1 ==> 71c655a6680ed765c398e5e7d753b58571381d5a (PR)
Upgrade the nodes to version: 71c655a6680ed765c398e5e7d753b58571381d5a
framework_upgrade::framework-upgrade::full-framework-upgrade : committed: 4586 txn/s, latency: 7153 ms, (p50: 7700 ms, p90: 9900 ms, p99: 11500 ms), latency samples: 169700
5. check swarm health
Compatibility test for aptos-node-v1.5.1 ==> 71c655a6680ed765c398e5e7d753b58571381d5a passed
Test Ok

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