feat(rde): add Remote Development Environment management commands

[evoxmusic]

Summary

• Add qovery rde command group for managing Remote Development Environments (RDE), enabling platform teams to provision isolated, pre-configured dev environments from blueprint templates
• Implement 21 new command files covering blueprint management, RDE lifecycle, bulk operations, and advanced features (upgrade, urls, logs, info)
• Use environment variables (BLUEPRINT_PROJECT_ID at project level, BLUEPRINT_KEY at environment level) for blueprint identification -- no naming convention required

Architecture

Identification Model

Blueprint Project
  ├── Project-level env var: BLUEPRINT_PROJECT_ID = <own project ID>
  └── Blueprint Environment
      └── Env-level env var: BLUEPRINT_KEY = <own project ID>

Child Project (cloned RDE)
  └── Child Environment (cloned from blueprint)
      └── Env-level env var: BLUEPRINT_KEY = <blueprint project ID>  ← different from own project

Discovery logic:

• BLUEPRINT_KEY == own project ID → blueprint master
• BLUEPRINT_KEY != own project ID → child of that blueprint

Command Tree

qovery rde
  ├── blueprint
  │   ├── create   --project <name>
  │   ├── list     [--json]
  │   ├── delete   --project <name>
  │   ├── status   --project <name>
  │   ├── deploy   --project <name> [--watch]
  │   └── stop     --project <name> [--watch]
  ├── create       --blueprint <name> --name <rde-name> [--email] [--skip-rbac] [--skip-invite] [--skip-deploy]
  ├── list         [--blueprint <name>] [--json]
  ├── status       --name <rde-name>
  ├── start        --name <rde-name> [--watch]
  ├── stop         --name <rde-name> [--watch]
  ├── delete       --name <rde-name>
  ├── stop-all     [--blueprint <name>]
  ├── start-all    [--blueprint <name>]
  ├── delete-all   --confirm [--blueprint <name>]
  ├── upgrade      [--name <rde-name>] [--strategy image|reclone]
  ├── urls         [--blueprint <name>]
  ├── logs         --name <rde-name>
  └── info

RDE Provisioning (rde create) Steps

1. Create project rde-<name> with description
2. Create RBAC role RDE-<name> with scoped permissions (optional)
3. Clone blueprint environment into new project
4. Handle TTL job from blueprint
5. Invite developer via email (optional)
6. Trigger deployment (optional)

API Methods Used

Uses the qovery-client-go typed client throughout (no raw HTTP calls):

• ProjectsAPI for project CRUD
• EnvironmentActionsAPI for clone, deploy, stop
• EnvironmentMainCallsAPI for delete, status
• OrganizationCustomRoleAPI for RBAC role management
• MembersAPI for member invitation
• VariableMainCallsAPI for blueprint identification via env vars
• ApplicationMainCallsAPI for workspace URL resolution
• JobsAPI / JobMainCallsAPI for TTL job handling
• OrganizationApiTokenAPI for cleanup

Testing

• Binary builds cleanly: go build
• All cmd package tests pass: go test -tags testing ./cmd/...
• Pre-existing test failure in utils/context_test.go (unrelated undefined symbols) -- not introduced by this PR