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

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)

The issue names no files, tests, or entry points. Start by reviewing PR #740 and the operator's release/versioning process, then determine how compatibility between the operator, pulpcore/galaxy packages, and container image should be represented. Done means the version relationship and compatibility expectations are defined and consistently surfaced for troubleshooting and upgrades.