Enhancement: Support Kubernetes Ingress to make use of potential existing Ingress Controllers

[jiglesia3]

Is your feature request related to a problem? Please describe. I'm having trouble creating a working Ingress to access the OneUptime UI. My cluster already has an ingress controller since a Kubernetes cluster is capable of hosting multiple applications, but since OneUptime's Helm Chart creates a separate LoadBalancer service with no Ingress resource by default, I'm unable to make use of my existing ingress controller. I've tried changing the oneuptime-nginx service type to ClusterIP as part of my troubleshooting so far.

Describe the solution you'd like A solution similar to https://github.com/OneUptime/oneuptime/issues/975 (the configuration provided in this issue is no longer applicable since the OneUptime services have changed since then) or a consolidation of images and services. Any documentation would be appreciated as well.

Describe alternatives you've considered A consolidation of images and services might require more of a refactor, but other open-source products I've deployed via Helm Chart typically include an Ingress resource.