fix(deploy): recreate deployment if selector changed

[ebaron]

This PR modifies the Deployment update code to detect when the immutable selector has changed. When this is detected, the operator deletes the deployment and recreates it. With this change it should be possible to upgrade from 2.0 to 2.2, the deployment selectors were changed in 2.1. I built a catalog image to help test this upgrade scenario: quay.io/ebaron/cryostat-operator-catalog:selector-fix-01.

To test:

1. Create the following objects:

apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
    name: cryostat-catalog
    namespace: openshift-marketplace
spec:
    sourceType: grpc
    image: quay.io/ebaron/cryostat-operator-catalog:selector-fix-01
    displayName: Cryostat Catalog
    publisher: Cryostat Authors
    updateStrategy:
        registryPoll:
            interval: 10m

apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
    name: cryostat-operator-group
    namespace: cryostat-operator-system
spec:
    targetNamespaces:
    - cryostat-operator-system

apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
    name: sub-to-cryostat-operator
    namespace: cryostat-operator-system
spec:
    channel: alpha
    name: cryostat-operator
    source: cryostat-catalog
    sourceNamespace: openshift-marketplace
    installPlanApproval: Manual
    startingCSV: cryostat-operator.v2.0.1-dev
    config:
        env:
        - name: RELATED_IMAGE_CORE
          value: quay.io/ebaron/cryostat:before-db

2. Approve the install plan for cryostat-operator.v2.0.1-dev.
3. Create a Cryostat instance.
4. Approve the install plan to upgrade to cryostat-operator.v2.2.0-dev.
5. The Cryostat deployment selector should have the component label:

kubectl get -ojsonpath='{.spec.selector}' deploy cryostat-sample | jq
{
  "matchLabels": {
    "app": "cryostat-sample",
    "component": "cryostat",
    "kind": "cryostat"
  }
}

6. The upgraded Cryostat application should function as normal.

Fixes: #433, #388

[andrewazores]

Makes sense and worked well in crc. Only hiccup was that the 2.0.1 installation had a broken Cryostat instance because the AUTH_MANAGER env var had the wrong fully-qualified classname (package has moved between versions), but I don't think that's relevant for this PR.

[tthvo]

Looks good! I tested on Cluster Bot with OCP 4.11.1 and worked as expected. Also noticed the crashing for 2.0.1, but select is updated expected :D