feat(deploy): drop the IaC layer, and make both apps runnable as containers

Moving the issuer's state into Postgres removed the last thing that tied
either app to one hosting provider. What was left was a deployment tool
describing resources that no longer existed — so this replaces it with
`wrangler`, which is what actually deploys a Worker, and adds a second way
to run each app that involves no provider at all.

Each app now has a `wrangler.jsonc` with an environment per stage, and a
`Dockerfile` beside it. The handler is the same one in both cases; what
differs is only where its settings come from. Two of them gained a second
spelling so that nothing has to branch on the runtime: Postgres arrives as
a pooled binding or as `DATABASE_URL`, and the route to the issuer is a
service binding or `AUTH_INTERNAL_URL`.

That last one is new, and it is a split the binding was already making
without saying so. `AUTH_ISSUER_URL` has to be the issuer's public name,
because it is compared literally against every token's `iss` claim — but
the public name is often not routable from inside a deployment. So the
name and the route are two settings now rather than one that cannot be
both.

DNS moves out of code and into `docs/dns.md`, which lists every hostname
and what it is for. Six records that change roughly never did not need a
tool, and the table outlives whatever is answering the names — which is
the point, since some of them will stop being Workers. The sandbox
hostnames are hyphenated rather than nested for the same reason: a
certificate covering `*.nestri.io` covers one label and not two, so
`api-sandbox.nestri.io` can become an ordinary origin later without a
certificate having to be ordered for it first.

Also drops `EMAIL_DEV_LOG` from committed configuration into `.dev.vars`,
which `wrangler deploy` cannot upload. Printing a live sign-in code to a
log should not be one forgotten override away from production.

README.md

@@ -66,7 +66,7 @@ Source and the full story: [`apps/nesdoctor`](apps/nesdoctor).
 Two halves that meet over the network and share very little else, plus one
 thing that runs on your own machine.
 
-### The control plane — TypeScript, on Cloudflare Workers
+### The control plane — TypeScript
 
 | | |
 |---|---|
@@ -75,8 +75,10 @@ thing that runs on your own machine.
 | [`packages/core`](packages/core) | The domain: every table, every operation, no HTTP. |
 | [`packages/auth`](packages/auth) | Shared auth types and subjects. |
 
-Postgres for state, [Alchemy](https://alchemy.run) for infrastructure. See
-[`docs/alchemy.md`](docs/alchemy.md).
+Postgres for state. Both run on Cloudflare Workers today and as ordinary
+containers wherever you like — one handler each, no infrastructure-as-code, and
+a `Dockerfile` in each app. See [`docs/deploy.md`](docs/deploy.md) and
+[`docs/dns.md`](docs/dns.md).
 
 ### The guest — Rust, inside the box
 
@@ -112,7 +114,10 @@ sandboxes, one GPU" possible instead of one tenant per card.
 
 ```sh
 bun install
+docker compose up postgres   # the database
+bun run db:migrate           # schema
 bun dev                      # control plane, local Cloudflare runtime
+docker compose up --build    # or: the whole control plane as containers
 
 cargo build --workspace      # guest components
 cargo test --workspace