Make synthetic handle resolvable under atproto rules
The interactive mode's printed handle was
`fake-client-under-test.<host>`, but DNS for that subdomain is not
something the operator controls (e.g. on a tunnelled funnel host).
A real public client typing the printed handle would fail both
atproto handle-resolution paths: DNS TXT on `_atproto.<subdomain>`
and HTTPS GET on `https://<subdomain>/.well-known/atproto-did` both
go nowhere.
The handle is now the active base URL's host, which by definition
routes to the fake AS, and the AS serves
`/.well-known/atproto-did` returning the synthetic DID as plain
UTF-8. The HTTPS-fallback resolution path now succeeds end-to-end
against the fake AS itself.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>