Should add BUILDMAN_HOSTNAME in config.yaml by operator with managed route component

Description of problem:

Currently we need to add BUILDMAN_HOSTNAME in config.yaml manually when configure builder. But if customer deploy quay by operator with managed route component, the buildman route is created by operator. That means should add BUILDMAN_HOSTNAME in config.yaml by operator automatic, customer do not need to handle this parameter manually

Version-Release number of selected component (if applicable):

registry-proxy.engineering.redhat.com/rh-osbs/quay-quay@sha256:248988b8d20b66572e4123ce85424f6e34eac1e670306a0bad6d30b702f3aba1
registry-proxy.engineering.redhat.com/rh-osbs/quay-quay:v3.4.0-40

registry-proxy.engineering.redhat.com/rh-osbs/quay-quay-builder-qemu-rhcos@sha256:f62fc1b17808a28242f5cf86940cf46298d56293429c17c0bb1d11a4bd8da17d
registry-proxy.engineering.redhat.com/rh-osbs/quay-quay-builder-qemu-rhcos:v3.4.0-13

How reproducible:

Always

Steps to Reproduce:
1. Prepare bare metal OCP

2. Create custom bundle secret and CR to deploy quay

3. check status

Actual results:

operator does not add BUILDMAN_HOSTNAME in config.yaml automatic

Expected results:

Should add BUILDMAN_HOSTNAME in config.yaml by operator automatic

Additional info:

Reference: https://github.com/quay/quay-docs/blob/master/modules/proc_use-quay-build-workers-dockerfiles.adoc#openshift-routes-limitation