[WIP] Validate agent-sandbox v0.5 rc1 adaptation

[ranxi2001]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Fork-only CI validation for the experimental agent-sandbox v0.5.0rc1 / v1beta1 adaptation.

This PR intentionally targets the fork base branch release-agent-sandbox-v05-base so CI only validates the v0.5 rc1 delta on top of the current volcano-sh#387-compatible baseline. It is not an upstream review request.

Main changes in the delta:

• Update AgentCube imports, schemes, and dynamic GVRs from agent-sandbox v1alpha1 to v1beta1.
• Replace direct Sandbox spec.replicas=1 with spec.operatingMode=Running.
• Replace warm-pool SandboxClaim templateRef usage with required warmPoolRef.
• Update workload-manager, agentd, and e2e tests for the v1beta1 API shape.

Which issue(s) this PR fixes:
Refs local Day18 validation notes only.

Special notes for your reviewer:

• Scope: fork-only CI validation; do not use this as an upstream PR.
• Base: release-agent-sandbox-v05-base at 5867183, matching the current fix: adapt code interpreter warm pool to agent-sandbox v0.4.6 volcano-sh/agentcube#387-compatible baseline.
• Head: test/agent-sandbox-v05-forward at ee1aecf.
• Prior local validation passed: workload-manager tests, non-e2e Go tests, race coverage, lint, gen-check, build-all, direct/warm-pool runtime e2e on a clean k3d cluster with the rc1 manifest, SDK, LangChain, MCP HTTP/stdio, and math-agent LLM e2e.
• Known limitation: this validates clean v1beta1 install behavior. It does not prove in-place CRD migration from clusters whose CRD status still contains storedVersions=["v1alpha1"].
• AI assistance: Used Codex to help inspect code, run validation, and prepare this fork-only CI PR. I reviewed and validated the changes.

Does this PR introduce a user-facing change?:

NONE