Implement proper JWT signature verification
Closes #1
- Add full ES256K signature verification using atrium-crypto
- Resolve issuer DID documents via atrium-identity
- Extract and verify publicKeyMultibase from #atproto verification method
- Convert keys to did:key format for signature verification
- Update atrium-xrpc-client to v0.5 for compatibility
- Remove explicit atrium-api dependency (pulled transitively)
Security impact: Prevents JWT forgery attacks by cryptographically
verifying that tokens are signed by the issuer's private key.