Create an app and deploy a revision programmatically via the Deno Deploy v2 REST API

Documented steps

1. Auth: Authorization: Bearer <dashboard-created token> against https://api.deno.com (v2 API).
2. Create an app: POST https://api.deno.com/v2/apps with body including at least {"slug":"my-app"}; note the returned app id/slug.
3. Create a revision (deployment): POST https://api.deno.com/v2/apps/{appId}/revisions.
4. Revision body carries: assets (file/symlink map, entries tagged kind "file" or "symlink"), entrypoint (main module path), optional env_vars ([{key,value}]), optional config (framework, install command, build command), and production (boolean or object with domains/databases) to target the production timeline.
5. Poll revision status: GET https://api.deno.com/v2/revisions/{revisionId}; list revisions: GET https://api.deno.com/v2/apps/{appId}/revisions.
6. Update app config later with PATCH https://api.deno.com/v2/apps/{appId}; delete with DELETE https://api.deno.com/v2/apps/{appId}.
7. Validate exact request/response field shapes against https://api.deno.com/v2/openapi.json before building a client - the narrative docs do not enumerate them.
8. Official docs: https://api.deno.com/v2/openapi.json ; https://docs.deno.com/deploy/reference/apps/ ; https://docs.deno.com/deploy/migration_guide/