fix: preserve existing annotations when updating managed secret

[minuchi]

Description 📣

This pull request fixes #1930 where the annotations on a managed Kubernetes secret were being reset during the update process. With this change, we ensure that existing annotations are preserved and only the ETag annotation is updated.

• Fixed the bug where updating the managed secret would reset all annotations. Now, only the ETag annotation is updated, preserving existing annotations.

Type ✨

• Bug fix
• New feature
• Breaking change
• Documentation

Tests 🛠️

1. Deploy the Kubernetes operator.
2. Check the annotations on the managed secret before updating.
3. Trigger an update.
4. Verify the annotations on the managed secret after the update.

Before the fix:

• Before update (annotations present)
  
• After update before the fix (annotations reset)
  

After the fix:

• After update with the fix (annotations preserved)
  

---

• I have read the contributing guide, agreed and acknowledged the code of conduct. 📝

[maidul98]

nice fix

[maidul98]

When this is done https://github.com/Infisical/infisical/actions/runs/9455645624, you can update your values file for helm to use the new image tag.

The new image should be tagged v0.5.3 here https://hub.docker.com/r/infisical/kubernetes-operator/tags