Adapt the existing Opstrace DevVM framework to create a VM-based testing environment for Container Registry E2E testing, replacing GDK with GitLab Orchestrator for improved stability and production-like deployment. **Technical Approach:** * Reuse Opstrace DevVM framework code from https://gitlab.com/gitlab-org/opstrace/devvm * Integrate GitLab Orchestrator instead of GDK for GitLab instance deployment * Set up Kind cluster within VM for Kubernetes-based registry deployment * Configure wireguard network + load-balancer for GitLab ↔️ GOB stack communication * Use Helm charts for registry deployment (matching staging/dedicated approach) **Key Benefits:** * More stable than GDK-based approach (avoiding issues like the Rails router bug) * Production-like deployment using Helm charts and Kubernetes * Reuses proven framework from Opstrace team * Supports both local development and CI execution * Enables cross-stack testing (GitLab + Registry workflows) **Acceptance Criteria:** * [ ] DevVM environment deployable with single command * [ ] GitLab Orchestrator successfully deploys GitLab instance in Kind cluster * [ ] Container Registry deployed via Helm chart within the same environment * [ ] Network connectivity established between GitLab and Registry components * [ ] Environment supports both local development and CI pipeline execution * [ ] Documentation covers setup process and troubleshooting * [ ] Framework ready for basic smoke tests **Technical Notes:** * Network configuration: wireguard + Kind cluster port forwarding + load-balancer * Deployment method: Helm charts (not embedded registry like in GDK) * Target similarity to dedicated/staging environments for better test validity