AWS dynamic secret revoke not re-created

**Describe the bug**
We have for security reason to revoke all our aws `iam_user`.
We have made it from the vault CLI.

But the VSO not update the secret automatically.

**To Reproduce**
Steps to reproduce the behavior:
1. deploy a VaultDynamicSecret that use an AWS dynamic creds
2. Wait the secret and `iam_user`creation
3. run `vault lease revoke --tls-skip-verify -force -prefix aws/creds`
5. AWS iam user is well deleted
6. but the Dynamic secret is not update and the iam user is not re-created (i have waited for 10min)

This seems related to the horizon that is very far.

**Expected behavior**
The revoke is propagated to the VaultDynamicSecret and a new Secret is generated with a new iam user

**Environment**
* Kubernetes version:
* Distribution or cloud vendor (OpenShift, EKS, GKE, AKS, etc.):
* Other configuration options or runtime services (istio, etc.):
* vault-secrets-operator version:

**Additional context**
Add any other context about the problem here.

Start by reproducing the behavior with a VaultDynamicSecret using AWS dynamic credentials, then run the documented `vault lease revoke --tls-skip-verify -force -prefix aws/creds` command and observe the operator. Done means the revoke is detected, the dynamic Secret is refreshed, and a new AWS IAM user is created.

Written by the indexing model from the issue text.