multiple Owner reference on secret with cluster-api and clusterresourceset

**Is your feature request related to a problem? Please describe.**
we deploy some secret generated by vaultstaticsecret with the clusterresourceset (cluster-api).
but VSS fail to sync secret due to 2 reference owner set on the secret

**Describe the solution you'd like**
VSO have to check if the owner is present on the list but not exact match

**Describe alternatives you've considered**
-

**Additional context**
here is an error sync log
```
Failed to update k8s secret: invalid ownerReferences, refs=[]v1.OwnerReference{v1.OwnerReference{APIVersion:"secrets.hashicorp.com/v1beta1", Kind:"VaultStaticSecret", Name:"osc-cloud-contr
oller-manager-secret", UID:"8d29d9be-6076-4a43-bb6a-1e33bfb50ea6", Controller:(*bool)(nil), BlockOwnerDeletion:(*bool)(nil)}, v1.OwnerReference{APIVersion:"addons.cluster.x-k8s.io/v1beta1", Kind:"ClusterResourceSet", Name:"osc-cloud-controller-manager", U
ID:"b3f06448-83dd-4a7e-8fa5-7ff58c09340d", Controller:(*bool)(nil), BlockOwnerDeletion:(*bool)(nil)}}
not the owner of the destination Secret devops-b/osc-cloud-controller-manager-secret
```

Start by tracing the VaultStaticSecret sync path that updates the destination Secret and the ownerReferences validation shown in the log. Reproduce the ClusterResourceSet plus VaultStaticSecret case and confirm it is done when a Secret with both owner references syncs without the invalid-owner error.

Written by the indexing model from the issue text.