Serve full atproto-required AS metadata field set
The fake AS's `/.well-known/oauth-authorization-server` document
was an RFC 8414–minimal subset, but the atproto OAuth profile
pins a much larger field set as mandatory. Conformant client
libraries validate the full set and reject any document missing
fields such as `client_id_metadata_document_supported`,
`authorization_response_iss_parameter_supported`, or
`subject_types_supported` — which surfaced as a generic
"Failed to resolve OAuth server metadata for issuer" error in
public clients pointed at the fake AS.
The served document now declares every field the atproto OAuth
spec requires, per
<https://atproto.com/specs/oauth#authorization-server>.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>