chore(deps): bump base64 from 0.22.1 to 0.23.0 without simd-unsafe

base64 0.23.0 adds `simd-unsafe` to its default features, which disables the
crate's unconditional `#![forbid(unsafe_code)]`. Our call sites only ever build
the scalar `GeneralPurpose` engine, and that engine passes a no-op SIMD prefix,
so the SIMD engines are unreachable from here. Turning the default features off
keeps the dependency free of unsafe code and leaves the API we use unchanged.

ureq, termwiz and tungstenite still require base64 0.22.1, so both locks carry
two versions of the crate.

Author: erickochen

Cargo.lock

@@ -38,7 +38,9 @@ sha2 = "0.10"
 hmac = "0.12"
 quick-xml = { version = "0.41", features = ["serde", "serialize"] }
 rsa = { version = "0.9", features = ["sha2"] }
-base64 = "0.22"
+# default-features off drops the `simd-unsafe` feature, keeping base64 at
+# `#![forbid(unsafe_code)]`. We only ever use the scalar GeneralPurpose engine.
+base64 = { version = "0.23", default-features = false, features = ["std"] }
 libc = "0.2"
 log = "0.4"
 simplelog = "0.12"