chore(deps): bump rustfs-uring to 0.2.0 (#4730)

chore(deps): bump rustfs-uring to 0.2.0 from crates.io

rustfs-uring 0.2.0 is published on crates.io. It carries the read-driver
hardening from the backlog#1160 adversarial audit (cancel-safety and
graceful-degradation fixes on the Linux io_uring read path). The public
API ecstore consumes is unchanged — UringDriver::probe_and_start_sharded,
read_at, read_at_direct all keep their 0.1.0 signatures — so this is a
drop-in bump of the version requirement plus the lockfile entry.

The Cargo.lock change is intentionally scoped to the rustfs-uring package
only; unrelated lockfile drift is left for its own change.

Co-authored-by: heihutu <heihutu@gmail.com>

Cargo.lock

@@ -10032,9 +10032,9 @@ dependencies = [
 
 [[package]]
 name = "rustfs-uring"
-version = "0.1.0"
+version = "0.2.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "f93a938838b26259162f23283de9d02922dc7b66d3a3c48a4db6036a44e9cf29"
+checksum = "358fe7987fc6b4a98dd65d4f6a7785f4f1af41daf027d14ae4b5a94eadba6348"
 dependencies = [
  "io-uring",
  "libc",

crates/ecstore/Cargo.toml

@@ -141,11 +141,10 @@ aws-smithy-http-client.workspace = true
 metrics = { workspace = true }
 
 # Runtime-probed io_uring read backend (backlog#1104). Linux-only, from
-# crates.io once rustfs-uring 0.1.0 is published. The guard
-# scripts/check_no_tokio_io_uring.sh allows an explicit io-uring integration;
-# only the tokio "io-uring" runtime feature is banned.
+# crates.io. The guard scripts/check_no_tokio_io_uring.sh allows an explicit
+# io-uring integration; only the tokio "io-uring" runtime feature is banned.
 [target.'cfg(target_os = "linux")'.dependencies]
-rustfs-uring = "0.1.0"
+rustfs-uring = "0.2.0"
 
 [dev-dependencies]
 tokio = { workspace = true, features = ["rt-multi-thread", "macros", "test-util"] }