Delete the Consent runtime

Archives the runtime and removes runtime access. Legacy runtime deletion can delete its database. V2 historical consent records remain in shared storage; this action does not schedule their purge. The project remains available. Requires the current runtime ID and backend version from lifecycle metadata as an explicit target confirmation; stale values return CONFLICT. The response snapshot has item null after archival and does not confirm erasure of historical records. Requires consent.lifecycle.write, projects.read and projects.write, with an admin or owner role for update/upgrade, or an owner role for delete. Subject to rollout-agent-access-writes and allow-public-agent-writes. Organization API keys cannot call this operation.