[Common] Refactor and Document Ingress

[Ornias1993]

Is your feature request related to a problem? Please describe.
Currently we have Ingress and appIngress.
Ingress is the Ingress system we ported from upstream when initially creating the common chart
appIngress is our custom ingress system, which provides/adds support for multiple ingress-dicts and ingress types (tcp/udp)

This creates a number of problems:

1. We also might want a additionalIngress object, which contains a list of ingresses, so users can add unlimited custom ingresses. This would mean we end up with 3(!) ingresses
2. It creates a hard time getting the Unit-tests to work nicely, so we had to keep the Ingress checks out of the unit-tests for now
3. It creates more duplicate code than required, which might lead to significant mistakes in the future.

Describe the solution you'd like

• upstream Ingress is going to be removed
• appIngress is going to be renamed Ingress
• additionalIngress is added which can contain a list (but doesn't have to)
• We need to try if we can create one template for both Ingress and IngressRoute
• In case we can not (reasonably) create a single template for all ingress forms, we at least need to merge the two IngressRoutes Into one template
• Create an official standardised questions.yaml format for Ingress and document it
• Carefully document the ingress (Reverse Proxy) options in the questions.yaml

Describe alternatives you've considered
Leaving it as is.
Which does not solve the problems at all

Additional context

[Ornias1993]

As a big portion of the code resolves around the certificates, we might want to release this rework together with the certificate rework for next release of TrueNAS SCALE

[Ornias1993]

Closed, Solved in staging branch

[truecharts-admin]

This issue is locked to prevent necro-posting on closed issues. Please create a new issue or contact staff on discord of the problem persists