tie BMO commits for CAPM3RELEASEBRANCH variables

[Rozzii]

This commit:

• ties specific commit hashes of the BMO release tags for each pre-defined CAPM3RELEASEBRANCH variable in the lib/common.sh

The reason is that in case BMO release branch HEAD is used together with a specific BMO container image release tag in the same deployment, there is a chance that a e.g. some patch could introduce CRD misalignment between the unchanged container image and the moving release branch head thus causing BMO operations or even BMO bootstrapping to fail.

[Rozzii]

/test metal3-centos-e2e-integration-test-release-1-7 /test metal3-dev-env-integration-test-ubuntu-main

[tuminoid]

Alternatively, we could use release-0.x tag of the container image and Git branch both?

[Rozzii]

/test metal3-centos-e2e-integration-test-release-1-7 /test metal3-dev-env-integration-test-ubuntu-main

[Rozzii]

Alternatively, we could use release-0.x tag of the container image and Git branch both?

In capm3 e2e we could overwrite these as that is a test / ci use-case , but in dev-env imo the idea is to deploy the supported releases by default so in dev-env I would go the way I did.

[Rozzii]

/test metal3-centos-e2e-integration-test-release-1-7 /test metal3-dev-env-integration-test-ubuntu-main

[metal3-io-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kashifest

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/metal3-io/metal3-dev-env/blob/main/OWNERS)~~ [kashifest] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[Rozzii]

/test metal3-centos-e2e-integration-test-release-1-7 /test metal3-dev-env-integration-test-ubuntu-main

[Rozzii]

/test metal3-centos-e2e-integration-test-release-1-7