[#91] Update Route handling to comply with custom domains

Currently routes are created and have enforced values, as per operator's code.

Since the operator should support and maintain custom domains when required, example on the following Ticket RQF2102204, this MR goal is to update the Operator to act accordingly when that's the case.

To summarize:

• Route configuration remains the same when it's a *.cern or *.web.cern.ch domain
• Any other domain and TLS field is not enforced, leaving it to another component to do it. As of 07/09/2022 that would be the openshift-acme, that will change once this issue is handled but since the new component does not present enough maturity, there is no ETA for the new component.

chart/drupalsite-operator/templates/manager-deploy.yaml

@@ -35,6 +35,7 @@ spec:
         - --easystart-backup-name={{.Values.drupalsiteOperator.easystartBackupName}}
         - --supported-drupal-version-name={{.Values.drupalsiteOperator.supportedDrupalVersionName}}
         - --velero-backup-storage-location={{.Values.drupalsiteOperator.veleroBackupStorageLocation}}
+        - --wildcardDelegatedDomainsRegex={{.Values.drupalsiteOperator.wildcardDelegatedDomainsRegex}}
         command:
         - /manager
         image: {{ .Values.image | quote }}