Close #1 by removing integrated caching

[a-bashtannik]

Fix "kid" invalid, unable to lookup correct key error.

Criipto rotates the keys regularly and users get problems with KID values trying to decode the response using cached values.

Support comment:

Each time you receive a JWT with a kid value you haven't seen before, you should fetch new metadata (once).
If the kid is present in the new metadata, you should update your cache and validate the token.
If not, you should reject the JWT.

It means you shall never cache configuration to avoid incosistency.

This PR removes Cache calls.