/auth/revoke takes an access or refresh token and refuses it from then
on, on every node, until it would have expired. Each account keeps a
list of revoked tokens in the in-memory store; the list is cached with
the account's access token, and a revocation drops that cache entry
cluster-wide. A refresh token is also checked against the store when
redeemed. A token issued to a client is revoked only by that client,
with its secret if it has one; one that doesn't validate is answered
200 as the RFC asks. Both discovery documents list revocation_endpoint.
Closes#427