feat: add OpenDAL-backed GooseFS object store support

Add `goosefs://` scheme support to `vortex-cloud`, bridging Tencent Cloud
GooseFS through OpenDAL's `services::GooseFs` via `object_store_opendal`.

Rust changes:
- `vortex-cloud`: new `goosefs` Cargo feature and `opendal::goosefs` module
  with `GoosefsConfig`, `make_goosefs_store`, and URL-to-config translation
  (master_addr from properties -> URL authority -> GOOSEFS_MASTER_ADDR env)
- `vortex-cloud/src/registry`: extend OpenDAL cfg gates to include `goosefs`
- 7 unit tests covering missing master_addr, URL authority, env fallback,
  property override, HA mode, and explicit config construction

Python bindings:
- `vortex-python`: new `GoosefsStore` pyclass with keyword-only options
  (root, block_size, chunk_size, write_type, auth_type, auth_username)
- `AnyVortexStore` accepts `GoosefsStore` in `read_url` / `write`
- Python store module `vortex.store._goosefs` with graceful ImportError
  fallback when the `opendal` feature is not enabled
- Type stub (`.pyi`) for `GoosefsStore` constructor

Dependency note: goosefs-sdk v0.1.8 is pulled transitively via
opendal-service-goosefs v0.57.0; no direct workspace dependency added.

Signed-off-by: XuQianJin-Stars <forwardxu1211@gmail.com>

Author: XuQianJin-Stars

Cargo.lock

@@ -52,8 +52,15 @@ oss = [
     "object_store/cloud",
     "opendal/services-oss",
 ]
+# Tencent Cloud GooseFS, the `goosefs://` scheme.
+goosefs = [
+    "dep:opendal",
+    "dep:object_store_opendal",
+    "dep:tracing",
+    "opendal/services-goosefs",
+]
 # Every OpenDAL-backed service.
-opendal = ["cos", "oss"]
+opendal = ["cos", "oss", "goosefs"]
 
 [lints]
 workspace = true

vortex-cloud/Cargo.toml

@@ -10,8 +10,8 @@
 //!   out of environment variables case-insensitively, matching how the `object_store` `from_env`
 //!   builders behave.
 //! * `opendal` supplies stores for cloud services the `object_store` crate does not implement
-//!   natively — Tencent Cloud COS and Alibaba Cloud OSS — bridged through
-//!   `object_store_opendal`.
+//!   natively — Tencent Cloud COS, Alibaba Cloud OSS, and Tencent Cloud GooseFS — bridged
+//!   through `object_store_opendal`.
 //!
 //! Every Vortex language binding resolves URLs through this one crate, so a scheme added here is
 //! reachable from Python, Java and DuckDB alike.
@@ -25,12 +25,13 @@
 //!   HTTP) it resolves URLs to.
 //! * `cos` — Tencent Cloud COS, the `cos://` scheme.
 //! * `oss` — Alibaba Cloud OSS, the `oss://` scheme.
+//! * `goosefs` — Tencent Cloud GooseFS, the `goosefs://` scheme.
 //! * `opendal` — every OpenDAL-backed service above.
 //!
 //! The `registry` feature picks up whichever OpenDAL services are enabled, so a consumer that
 //! turns on `oss` gets `oss://` resolution without touching its own scheme matching.
 
-#[cfg(any(feature = "cos", feature = "oss"))]
+#[cfg(any(feature = "cos", feature = "goosefs", feature = "oss"))]
 pub mod opendal;
 #[cfg(feature = "registry")]
 mod registry;