Add `verificationMethod` to synthetic DID document
atproto's identity spec requires every DID document to include a
`verificationMethod` entry with id `#atproto` and type `Multikey`.
The synthetic DID document was missing it, so strict atproto
identity resolvers (atrium, `@atproto/identity`, etc.) rejected
the document during handle resolution and the OAuth flow never
reached the fake AS.
The DID document now publishes a Multikey derived from a fixed
secp256k1 seed and adds the matching suite contexts
(`multikey/v1` and `suites/secp256k1-2019/v1`) to `@context`. The
fake AS never signs anything with the key — it is published only
to satisfy the spec — and the seed is fixed so the key is stable
across runs.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>