release-manager: switch reqwest from native-tls to rustls-tls

The musl static build in `release.yml` failed on the v0.0.0-test
smoke tag because release-manager transitively pulls in
`openssl-sys` via reqwest's default `native-tls` backend, and
musl-targeted OpenSSL isn't available on the runner:

  error: failed to run custom build command for `openssl-sys v0.9.109`
  warning: openssl-sys@0.9.109: Could not find directory of OpenSSL
  installation, and this `-sys` crate cannot proceed without this
  knowledge.

Fix: `default-features = false` + `rustls-tls` on reqwest. Pure-Rust
TLS, no system OpenSSL link, no `*-sys` crate compiled — same
pattern mina-bench-upload already uses for its influxdb2 client.

Cargo.lock regenerated; verified `openssl-sys`, `native-tls`, and
`hyper-tls` are all gone from the lockfile.

This is the last remaining gap before the release workflow can ship
a static-musl `.deb` portable across bullseye/focal/jammy/noble/
bookworm. Push v0.0.0-test (force) after this lands to retest.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: dkijania

release-manager/Cargo.lock

@@ -33,7 +33,12 @@ hex = "0.4"
 
 [dependencies.reqwest]
 version = "0.11"
-features = ["json", "stream"]
+# default-features = false drops the native-tls / openssl-sys
+# dependency that breaks musl static builds. `rustls-tls` gives us
+# back HTTPS support in pure Rust, matching the pattern
+# mina-bench-upload already follows with its influxdb2 feature pin.
+default-features = false
+features = ["json", "stream", "rustls-tls"]
 
 [dev-dependencies]
 tokio-test = "0.4"