Complete deployment API lifecycle support

[heimanba]

What changed

• add native deployment list, pause, and unpause support for Qoder and Claude
• expose remote deployment listing and lifecycle commands through the SDK and CLI
• split deployment create/update mapping so removed resources, vaults, descriptions, metadata, and Qoder environment variables are reconciled correctly
• add Qoder-only environment_variables validation and fix Qoder deployment conflict adoption
• correct deployment CLI help and document the new commands

Why

The deployment adapters covered create, get, update, archive, and run, but omitted documented list/pause/unpause operations. The update path also reused the create payload, so fields removed from declarative config could remain on the remote deployment while apply reported success.

User impact

Users can inspect native provider deployments, pause or resume schedules, and configure Qoder deployment-level environment variables. Updates now reconcile clearable fields instead of silently preserving stale remote values. Removing an existing schedule fails with actionable archive/recreate guidance because neither provider documents a schedule-clearing update value.

Validation

• full pre-push verification profile passed
• all workspace typechecks passed
• architecture dependency and semantic checks passed
• SDK, CLI, playbooks, WebUI, and server test suites passed
• live Qoder and Claude E2E: create, remote list, get, update, pause, unpause, run, destroy, and remote cleanup verification
• Qoder environment_variables normalization and Claude/Qoder update results verified through direct provider GETs