Fix registry facade not being able to start up in preview environment

[Furisto]

Description

Remove ownerReferences as they still reference the old secret name, which makes Kubernetes accept the creation of the secret, but then it vanishes without a trace. Registry-facade then tries to mount the non existing secret.

 ownerReferences:
  - apiVersion: cert-manager.io/v1
    blockOwnerDeletion: true
    controller: true
    kind: Certificate
    name: harvester-fo-ws-class-env
    uid: 1ab08d7c-78f2-43ae-ad3a-fc0a67d06bde

Related Issue(s)

n.a.

How to test

Preview environment should get into ready state

Release Notes

NONE

[Furisto]

The last build is green: https://werft.gitpod-dev.com/job/gitpod-custom-fo-remove-owner-refs.2
The checks show the wrong status.

[Furisto]

/werft run

👍 started the job as gitpod-build-fo-remove-owner-refs.1
(with .werft/ from main)

[Furisto]

/werft run -j .werft/build.yaml -s .werft/util/certs.ts -f -a with-clean-slate-deployment=true

[Furisto]

/werft run -j .werft/build.yaml -s .werft/util/certs.ts -f -a with-clean-slate-deployment=true

👍 started the job as gitpod-build-fo-remove-owner-refs.2
(with .werft/ from main)

[mustard-mh]

Works well in this job👍 https://werft.gitpod-dev.com/job/gitpod-build-hw-vs-port.6/logs

[vulkoingim]

/werft run github -j ./werft/build.yaml -s .werft/util/certs.ts -a updateGitHubStatus=gitpod-io/gitpod

👍 started the job as gitpod-build-fo-remove-owner-refs.3
(with .werft/ from main)

[Furisto]

/werft run github -j ./werft/build.yaml -s .werft/util/certs.ts -a updateGitHubStatus=gitpod-io/gitpod

👍 started the job as gitpod-build-fo-remove-owner-refs.4
(with .werft/ from main)