feat(io): compile GooseFS metadata and page caches

[XuQianJin-Stars]

Depend on opendal-service-goosefs 0.59.2 directly so Cargo unifies
metadata-cache and page-cache-io-uring into the same GooseFS client
build as opendal/services-goosefs.

Pin goosefs-sdk 0.2.2 in Lance (no OpenDAL bump). OpenDAL 0.59.2's
^0.2.1 requirement unifies onto 0.2.2. 0.2.2 keeps
metadata_cache_enabled off by default, matching Java
goosefs.user.metadata.cache.enabled, so compiling metadata-cache no
longer serves a 10-minute stale FileInfo for overwritten
_refs/tags/.json.

This compiles the caches into lance-io, pylance, and lance-jni whenever
the goosefs feature is enabled. Runtime behavior stays off until
configured:

• Metadata cache: off by default. Set GOOSEFS_METADATA_CACHE_ENABLED=true to opt in
• Page cache: off by default; enable with
  GOOSEFS_USER_CLIENT_CACHE_ENABLED=true and
  GOOSEFS_USER_CLIENT_CACHE_DIRS / goosefs.user.client.cache.dirs
• page-cache-io-uring uses io_uring on Linux and tokio::fs elsewhere

Build with GooseFS (these also compile metadata-cache and page-cache-io-uring):

# Rust (goosefs is already in lance default features)
cargo build -p lance --features goosefs

# Python / pylance (python/Cargo.toml already enables lance/goosefs)
cd python && uv run make build

# Java JNI (dir-goosefs enables lance-io/goosefs)
cargo build --manifest-path java/lance-jni/Cargo.toml
# or: cd java && ./mvnw compile

Test plan

• cargo test -p lance-io --features goosefs --lib object_store::providers::goosefs
• cargo check --manifest-path python/Cargo.toml
• cargo check --manifest-path java/lance-jni/Cargo.toml
• Confirm goosefs-sdk in Cargo.lock is 0.2.2 and pulls lru / foyer / io-uring

[lance-gatekeeper]

✅ Gate recommendation: approve.

The rebased revision preserves the verified behavior: goosefs-sdk resolves to 0.2.2, both GooseFS caches are compiled, and metadata and page caching remain runtime opt-ins. Mutable tag freshness therefore remains protected by default.