test: add RustFS e2e integration harness

[GatewayJ]

Type of Change

• New Feature
• Bug Fix
• Documentation
• Performance Improvement
• Test/CI
• Refactor
• Other: N/A

Related Issues

N/A

Summary of Changes

• Simplify the RustFS Operator e2e workflow to four operator-facing live targets: e2e-live-create, e2e-live-run, e2e-live-update, and e2e-live-delete.
• Keep lower-level kind/deploy/rollout behavior behind the Rust e2e helper while preserving dedicated-context live guards.
• Add/update standalone e2e crate quality gates in CI and script-test coverage for the reduced Make target surface.
• Update e2e/README.md to document the reduced live workflow and local verification path.

Checklist

• I have read and followed the CONTRIBUTING.md guidelines
• Passed make pre-commit (fmt-check + clippy + test + console-lint + console-fmt-check)
• Added/updated necessary tests
• Documentation updated (if needed)
• CHANGELOG.md updated under [Unreleased] (if user-visible change; N/A for this e2e harness)
• CI/CD passed

Impact

• Breaking change (CRD/API compatibility)
• Requires doc/config/deployment update: updates e2e harness documentation and live workflow targets
• Other impact: N/A

Verification

# Non-live orchestration/static gates
make -n e2e-live-create
make -n e2e-live-update
make -n e2e-live-run
make -n e2e-live-delete
./scripts/test/script-test.sh
cargo fmt --all --check
cargo fmt --manifest-path e2e/Cargo.toml --all --check
cargo test --manifest-path e2e/Cargo.toml --no-run
cargo clippy --manifest-path e2e/Cargo.toml --all-targets -- -D warnings
cargo clippy --all-features -- -D warnings
cargo test --all
cargo test --manifest-path e2e/Cargo.toml --all-targets

# Live gate on dedicated kind-rustfs-e2e context
make e2e-live-run

GitHub Actions Continuous Integration / Test and Lint passed on PR head e0ca852bcaf3fd4575d21d030e2722f82053ba50.

Additional Notes

Replaces #119 with a branch based directly on current origin/main to avoid a duplicate squash-equivalent upstream commit.

---

Thank you for your contribution! Please ensure your PR follows the community standards (CODE_OF_CONDUCT.md) and sign the CLA if this is your first contribution.