Feature Request: Force Synchronization of Secrets Managed by Other Resources

[marcosmamorim]

I'm proposing a new feature for the bitwarden-k8s-secrets-manager that would add the capability to force synchronize secrets even if they are currently managed by other resources. This feature would be particularly useful for migration scenarios where secrets initially set up by other applications (like Helm for Kubernetes deployments) need to be taken over and managed by bitwarden-k8s-secrets-manager.

Use Case Example:

Consider a scenario where an application is deployed using Helm, which automatically creates several secrets. Over time, it may become necessary to migrate the management of these secrets to bitwarden-k8s-secrets-manager. Currently, if a secret is already managed by Helm, there's no straightforward way to have bitwarden-k8s-secrets-manager take over without manual intervention.