Ask IAM Auth for replicated refresh token state on introspect
Once Workhorse routes every refresh grant to IAM Auth, IAM Auth can consume a replicated Doorkeeper refresh token without Rails seeing it. /oauth/introspect now asks IAM Auth over the new GetState RPC (gitlab-org/auth/iam!993 (merged)) and reports an unprefixed refresh token active only if both stacks agree, as proposal 011 describes. Closes #635135 (closed).
The check runs only after Doorkeeper authorizes the client and Rails already reports the token active, behind the iam_introspect_replicated_refresh_tokens flag. It fails closed: NOT_FOUND or an IAM error reports the token inactive. The first commit regenerates the vendored IAM gRPC stubs; review the second.
The Rails row is left as it is. After IAM Auth consumes a replicated refresh token, the row stays live in Rails, because replication runs in one direction only. The access token on that row stays valid until it expires, two hours by default, where Doorkeeper would have revoked it at refresh.