[CMSSE-730]: Fix docs and warning for redis cache config

[angusjf]

The config as I copied it from the readme didn't work - and there wasn't a warning for it just a failed pattern match.

I've created this mood board to explain the problem:

Could well be the case that I've misread something but gave it a go to fix it. Possibly pattern matching on :'Elixir.EncryptedRedisTokenCache' isn't very nice because I guess fully qualified or aliased module names wouldn't match - I can't think of a nicer solution though.

[cottinisimone]

Seems reasonable to me. Being that prima_auth0_ex, :redis, :enabled is deprecated there's no reason to let it live in the readme.

But maybe might be worth it to add another match after {true, nil} like:

{true, provider} ->
        Application.put_env(:prima_auth0_ex, :token_cache, provider)

?

Moreover, being that here you are, can you please fix the typo? It's written provieder XD.

If you think it's out of scope no worries, i'll open a card on our board with those changes

[angusjf]

But maybe might be worth it to add another match after {true, nil} like:

{true, provider} ->
      Application.put_env(:prima_auth0_ex, :token_cache, provider)

?

@cottinisimone I don't get it, the provider is read from config so why would I put it back in the config?

[cottinisimone]

But maybe might be worth it to add another match after {true, nil} like:

{true, provider} ->
      Application.put_env(:prima_auth0_ex, :token_cache, provider)

?

@cottinisimone I don't get it, the provider is read from config so why would I put it back in the config?

I'm just saying that some user might have an older version of auth0_ex so they might have enabled: true flag. If they set the provider it raise an exception. I'm just suggesting to gracefully handle this case so that it alerts you that the config is deprecated, but still it let you use the provider you put in the config