feat: olm deployment helper

[razvan]

Description

Part of: stackabletech/issues#666

This PR adds a new binary crate (olm-deployer) to the secret operator.
The binary is bundled in the resulting container image and is only used by the OLM.

How to test

Requirements:

1. An OpenShift cluster.
2. Checkout the branch secret-olm-deployer from the operators repo.
3. Clone the stackable-utils repo

Install the secret operator using OLM and the olm-deployer. From the stackable-utils repo, run:

$ ./olm/build-bundles.sh -c $HOME/repo/stackable/openshift-certified-operators -r 24.11.0 -o secret -d

The secret op and all it's dependencies should be installed and running in the stackable-operators namespace.

Note

The ClusterSertviceVersion is now using the olm-deployer binary instead of the shell script

This is the relevant part of the clusterservicedefinition.yaml file:

containers:
  - name: secret-operator-deployer
    image: "docker.stackable.tech/stackable/secret-operator:0.0.0-pr546"
    command: ["/usr/bin/bash"]
    args:
      - "-c"
      - "/usr/local/bin/olm-deployer run --dir /manifests --namespace $NAMESPACE --csv secret-operator.v24.11.0 --keep-alive"

Integration tests

First checkout release-24.11 branch of the secret operator repo. This is needed because secret-olm-deployer branch deploys the 24.11.0 op version. The fact that 24.11.1 is now latest doesn't matter.

$ ./scripts/run-tests --skip-operator secret --test-suite openshift

[NickLarsenNZ]

Is this an accidental left-over?

[NickLarsenNZ]

Partial review. Will try to give it a proper look tomorrow.

[NickLarsenNZ]

We should use expect instead of unwrap, and then write the expectation as the fist argument.

Suggested change

	x @ serde_json::Value::Null => {
	*x = serde_json::json!({});
	x.as_object_mut().unwrap()
	}
	x @ serde_json::Value::Null => {
	*x = serde_json::json!({});
	x.as_object_mut().expect("the empty object above is guaranteed to result in Some(serde_json::Map)")
	}

[adwk67]

🟢 Tested on Openshift:

--- PASS: kuttl (155.30s)
    --- PASS: kuttl/harness (0.00s)
        --- PASS: kuttl/harness/kerberos_krb5-1.21.1_openshift-true (27.30s)
        --- PASS: kuttl/harness/tls_openshift-true_rsa-key-length-2048 (67.93s)
        --- PASS: kuttl/harness/tls_openshift-true_rsa-key-length-3072 (34.65s)
        --- PASS: kuttl/harness/cert-manager-tls_openshift-true (93.66s)
        --- PASS: kuttl/harness/listener_openshift-true (44.16s)
PASS

[adwk67]

as we are now pushing to OCI, it is necessary to login first with:
docker login oci.stackable.tech and then supply username plus a CLI key obtained from User/Profile in the Harbor UI