deps: bump hmac 0.13 and sha2 0.11 together

[rearden-grok]

Summary

Dependabot #673 (sha2 0.11) and #674 (hmac 0.13) each fail because those crates must move together onto digest 0.11. This PR bumps both, and imports hmac::KeyInit so HmacSha256::new_from_slice still resolves. Tor SAFECOOKIE uses that HMAC.

Also in this bump:

• Node getrandom 0.3 → 0.4 (same fill call; store, net, and rpc were already 0.4).
• bitcoin requirement 0.32.101 → 0.32.102 (the lock was already there).
• Compatible lock updates: bitflags 2.13.2, cc 1.4.7, hex-conservative 0.2.3 / 1.3.0, hyper 1.11.1, smallvec 1.16.1, syn 3.0.6, zerocopy 0.8.57, and a few smaller ones.

Left where they are:

• bitcoin_hashes 0.14.101. 1.2.0 exists, and bitcoin 0.32 still requires 0.14.
• tokio-tungstenite 0.29. 0.30 exists, and axum 0.8 still depends on 0.29.
• getrandom 0.2 and 0.3 stay in the lock because rand_core 0.6 / 0.9 still need them.
• libc 1.0 is an alpha. We stay on 0.2.
• generic-array 0.14.7 and matchit 0.8.4 did not move under the current resolver.

Test plan

• cargo test -p rbitcoin-node --lib -- tor_ safecookie
• cargo clippy -p rbitcoin-node --all-targets -- -D warnings
• cargo deny check
• Required CI