Cache JWKS #10
Description
The refresh of JWKSs is currently done by always fetching the JWKS from Auth0.
We should evaluate whether to place some caching mechanism, as we did for the tokens fetched from Auth0.
This would allow us to keep working (especially for deploys/scaling) even if Auth0 was down.
On the down side it would add some delay to the propagation of new JWKS.
So far we decided this was not a high priority issue, as JWKS are probably served by a CDN, hence the danger of prolonged downtime should be limited.