Hosted cluster deployment, adjust get_random_hosted_cluster_name to work with multiple platforms

[DanielOsypenko]

Following the PR #9957
We need to adjust the get_random_hosted_cluster_name function

Comment from @dahorak:

I understood, that it is good to be able to match the hosted cluster somehow with the hosting cluster, but I'm not sure about this approach, because it is quite specific for the particular environment. I'm not sure, if it is possible, that we would like to run this on octo-argo environment (maybe that is not even sufficient, not sure), or wouldn't this be later used on other platforms as well - e.g. vSphere?
What about at least make the bm_name part optional? So it will not fail if the env_name will not match the expected form or will be missing. Since the last part of the cluster name is anyway random, there shouldn't be any conflict in the cluster name and the only drawback will be the fact, that it will not be directly visible where the cluster belongs to.
Another option which might be sufficient would be to make the whole part bmX configurable and add this configuration to the environment specific conf files.

[DanielOsypenko]

    registry_image = catsrc_data.get("spec").get("image")
    return registry_image.split(":")[-1]

same function:
@dahorak
Also I'm not sure, if it is applicable for the places, where this function is used, but this will not work correctly for GA version of ODF.
address this as well

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 30 days if no further activity occurs.

[github-actions]

This issue has been automatically closed due to inactivity. Please re-open if this still requires investigation.