Drop our own noobaa instance

It actually creates a conflict when using argo due to:

    spec.dbStorageClass is immutable and cannot be updated for volume "db"
    in existing StatefulSet "noobaa-core" since it requires volume recreate
    and migrate which is unsupported by the operator

The noobaa kind gets created automatically by the operator anyways, so
let's drop this. Tested this patch and I got a correctly working S3
backend and the noobaa default object:

    ❯ oc get noobaa -n openshift-storage
    NAME     S3-ENDPOINTS                    STS-ENDPOINTS                   SYSLOG-ENDPOINTS   IMAGE                                                                                                            PHASE   AGE
    noobaa   ["https://10.0.73.165:32283"]   ["https://10.0.73.165:31209"]                      registry.redhat.io/odf4/mcg-core-rhel9@sha256:b93834768ad50a259c534ba08991b2dbdc08f81a65642462e294a347166a87f7   Ready   26m

Author: mbaldessari