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.

.dockerignore

@@ -1,18 +1,18 @@
-# build/Dockerfile's context is the repo root (see build/Makefile), so this
-# keeps the daemon-side context transfer to what it actually COPYs: the
-# workspace manifests plus the five Rust members. Everything else here is
-# TypeScript/tooling the guest rootfs build never touches.
+# What no image in this repo ever wants: history, and build output produced
+# outside the container.
+#
+# This file used to also exclude the TypeScript half, because the guest rootfs
+# build was the only Dockerfile here. There are three now, and two of them are
+# the TypeScript half — so what is specific to one build moved next to that
+# build, as `<Dockerfile>.dockerignore`. Getting that wrong here is expensive
+# in a way that is hard to see: an excluded path is not an error, it is a
+# `COPY` that silently lands nothing.
 .git
 node_modules
 target
 build/output
-docs
-apps/api
-apps/auth
-packages
-*.md
-deno.lock
-bun.lock
-.env*
-.zed
-.github
+.env
+.env.*
+.wrangler
+dist
+.output