Use custom gateway ingress host in OpenShift tenant redirect URLs.

[akshitkumawat]

Summary

• When spec.template.gateway.ingress.host is set, the OpenShift gateway Route already uses that hostname, but OpenShift tenant redirectURL values in tenants.yaml were still built from the generated Route FQDN (tempo-<name>-gateway-<namespace>.<baseDomain>).
• Tenant redirect URLs now use the same effective hostname as the Route: the configured ingress host when present, otherwise the existing generated Route hostname.
• Default behavior is unchanged when no custom gateway ingress host is configured.

Test plan

• go test ./internal/manifests/gateway/
• Custom ingress host produces https://<custom-host>/openshift/<tenant>/callback
• No custom host still uses naming.RouteFqdn for redirectURL
• Multiple tenants share the same gateway host and keep tenant-specific callback paths (/openshift/dev/callback, /openshift/test/callback)
• Existing gateway unit tests continue to pass

[github-actions]

Signed commits report

1 of 1 commit between main and fix-custom-gateway-ingress-host-redirect could not be fully verified:

Commit	Author	Reason	Message
bdada814	Akshit Kumawat	unsigned	Use custom gateway ingress host in OpenShift tenant redirect URLs.

This repository requires all commits to be signed. See GitHub docs on commit signature verification.

[cla-assistant]

All committers have signed the CLA.

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}