Description of problem:

User has reported an issue about component label `app.kubernetes.io/component` clash between Vault-Secrets operator and Dev Spaces Oauth secret.

They are deploying Dev Spaces on openshift and labels are used to identify if a component is part-of the application, as VSO is grabbing the component label, It stops them using VSO operator and use a secret for Dev Spaces.

When creating a secret and deploying it with Vault Secrets Operator to enable `oauth` for devspaces the `app.kubernetes.io/component` label gets overwritten.

From VSO : 
    app.kubernetes.io/component: secret-sync

Required by Devspaces : 
    app.kubernetes.io/component: oauth-scm-configuration

They are running `Dev Spaces 3.24.1` version.

For reference, Below are the issues reported to upstream :

> https://github.com/eclipse-che/che/issues/23696

> https://github.com/hashicorp/vault-secrets-operator/issues/1045