feat(auth): auto retry on jwks key not found

[flaneur2020]

I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/

Summary

currently, we maintain a cache for the jwks keys, and use the cache to validate the jwt authentications.

however, the jwks endpoint may rotate at any time. if the client rotated with the latest jwt, we may get a key not found 401 error on jwt authentication until the next jwks refresh (by default, it's 30s).

this error can be auto-recovered after 30s, but we want to go a step further about this to make it not noticeable for users with retry.

this pr added a retry for refreshing the jwks endpoint after a key not found error. and to avoid flooding the jwks endpoint, it limited a retry_interval.

there's also a risk that the server rotates the jwks first, but the client still uses the older jwt. to mitigate this risk, this pr also buffered the earlier jwks keys in memory.

Tests

• Unit Test

Type of change

• New Feature (non-breaking change which adds functionality)

---

This change is