Setting ownerReference with controller:true
for Keycloak resources has disadvantages:
- `controller: true` should be set for resources created by a controller.
  For example, we create a Deployment, and the controller creates
  a ReplicaSet with an `ownerReference` to the Deployment.
  In our case, we create resources separately, and
  the Keycloak controller isn't responsible for their creation.
- ArgoCD doesn't remove resources with `controller: true`.
  It considers another controller responsible for them.
  If we remove the ArgoCD environment that contains KeycloakClient,
  this CR won't be removed by either ArgoCD or the Keycloak operator.

This change break automatic deletion of CRs
if related Keycloak/KeycloakRealm is removed.
Now it isn't responsibility of the keycloak operator.

Setting ownerReference with controller:true
for Keycloak resources has disadvantages:
- `controller: true` should be set for resources created by a controller.
  For example, we create a Deployment, and the controller creates
  a ReplicaSet with an `ownerReference` to the Deployment.
  In our case, we create resources separately, and
  the Keycloak controller isn't responsible for their creation.
- ArgoCD doesn't remove resources with `controller: true`.
  It considers another controller responsible for them.
  If we remove the ArgoCD environment that contains KeycloakClient,
  this CR won't be removed by either ArgoCD or the Keycloak operator.

This change breaks the automatic deletion of CRs
if related Keycloak/KeycloakRealm is removed.
Now, it isn't the responsibility of the keycloak operator.

Setting ownerReference with controller:true
for Keycloak resources has disadvantages:
- `controller: true` should be set for resources created by a controller.
  For example, we create a Deployment, and the controller creates
  a ReplicaSet with an `ownerReference` to the Deployment.
  In our case, we create resources separately, and
  the Keycloak controller isn't responsible for their creation.
- ArgoCD doesn't remove resources with `controller: true`.
  It considers another controller responsible for them.
  If we remove the ArgoCD environment that contains KeycloakClient,
  this CR won't be removed by either ArgoCD or the Keycloak operator.

This change breaks the automatic deletion of CRs
if related Keycloak/KeycloakRealm is removed.
Now, it isn't the responsibility of the keycloak operator.