Make route port configurable
https://gitlab.cern.ch/paas-tools/operators/gitlab-pages-site-operator/-/blob/a67d29ed/controllers/operator_methods.go#L119 hardcodes using the service's first port as the route's targetPort.
Following paas-tools/okd4-deployment/gitlab-pages-authenticating-proxy!5 (merged) we have multiple ports so it would be preferable to have the targetPort value configurable with a command-line argument and Helm value, so it is explicit that the operator needs to know the port. (and saves from looking up the service
)
After paas-tools/okd4-deployment/gitlab-pages-authenticating-proxy!5 (merged) is deployed the targetPort value can be the named port pages-proxy
but maybe best to use 8080
for now, which is already functional.