feat(relay): OAuth server metadata endpoint — GET /.well-known/oauth-authorization-server (MM-75)
Implements RFC 8414 OAuth 2.0 Authorization Server Metadata discovery so
Bluesky clients can find the relay's OAuth endpoints without hardcoding paths.
- New route: GET /.well-known/oauth-authorization-server returns JSON with
issuer, authorization_endpoint, token_endpoint, pushed_authorization_request_endpoint,
jwks_uri, and AT Protocol-required fields (dpop_signing_alg_values_supported,
token_endpoint_auth_methods_supported: ["none"])
- New db/oauth.rs: SQLite storage adapter (register_oauth_client, get_oauth_client)
against the existing oauth_clients table from Wave 1 schema
- Bruno request file added (seq: 12)
- Fix two pre-existing clippy lints in auth/mod.rs and create_did.rs surfaced
by the updated toolchain; cargo fmt applied across relay crate
atproto-oauth-axum (0.14.3) was evaluated but requires axum 0.8 (relay is on
0.7) and is an OAuth client crate, not a server crate — tracked as MM-154.