v0.82.1 — a client's token lifetime now reaches the id_token

Fixed

A client's token lifetime was hardcoded at 900 seconds for the id_token, so accessTokenTtl shortened only the access token — and a relying party that authenticates the ID token never sees that one.

Kubernetes is exactly that case: kubectl oidc-login presents the id_token as its bearer, the API server validates exp offline and never calls back, so for it the id_token's lifetime IS the revocation window. A client registered with a 300-second TTL was getting five minutes on a credential it does not present and fifteen on the one it does.

Nothing changes for a deployment that has configured nothing: the default is still 900.