[RFE] Bind operator version with pulpcore/galaxy package version and pulp container image version

[git-hyagi]

We should link the operator version with pulpcore package version. This will be helpful during troubleshooting, upgrading, and avoiding compatibility issues between the operator configs and pulpcore/galaxy version.

Some examples of scenarios in which this is very important:

• PR #740 was necessary because of an update on galaxy endpoint path (if someone has a similar issue how can we know if it happened because it is not using the newer image version or it is because of another error?)
• When we release a new feature (in pulpcore or galaxy) that is not compatible with the current settings of the operator, it would break the running environment (for example, with the release of domains we will probably need to update route/ingress configs and would need to update our docs with something like: operator:vX.Y.Z is compatible with pulp-minimal:vA.B.C and in pulp-minimal we should install pulpcore-A.B.C packages)

[fao89]

I realize it is more complicated than I thought, the operator default is pulp image with stable tag. If I s/stable/${PULPCORE_VERSION}/ then if the user changes the image to galaxy, it will break as galaxy won't have the ${PULPCORE_VERSION} tag

[dkliban]

For each 3.y.0 release of Pulpcore, a new version 3.y.0 release of pulp-operator should be made. Any bug fixes in the operator should produce pulp-operator 3.y.1+ release.

Before we can accomplish this we need to fix https://github.com/pulp/pulp-oci-images/issues/323