Don't wrap ResourceNotFoundException

If the secret is not on AWS Secrets Manager the client will throw a `ResourceNotFoundException` that will be wrapped in [`SecretCacheObject.__refresh`](https://github.com/aws/aws-secretsmanager-caching-python/blob/8b3ed311982096d6cb6a99ab33299ade3c9811b3/src/aws_secretsmanager_caching/cache/items.py#L97)

I think to **wrap `ResourceNotFoundException` is not good practice**: because after the client application has no way to understand that something is wrong in the configuration of Aws SM, and if you have a hook it will be triggered anyway even if an exception occurred and the value is None.
[the implementation of `SecretCacheHook` will receive `cached_obj = None` in the get method]

Inizia in src/aws_secretsmanager_caching/cache/items.py, in SecretCacheObject.__refresh, quindi leggi come SecretCacheHook riceve cached_obj nel percorso get. Conferma il comportamento attuale di wrapping per ResourceNotFoundException e considera completato il lavoro quando quell'eccezione viene preservata, in modo che gli errori di configurazione siano distinguibili e l'hook non venga invocato con None.

Scritto dal modello di indicizzazione a partire dal testo della issue.