Make Ingress optional and ingressClass configurable

[p4block]

A bigger rework of the chart comes to my mind but this suffices for my usecase.
Should be compatible with previous installs with no intervention.

Commenting on related things, fully decoupling the helmchart from gke/aws/do would be optimal, as there's really nothing that actually ties LiveKit to them. Ingress should also be decoupled from the loadbalancer, as TLS-terminating LBs can avoid the need for one if the user configured them but other people may use service+ingress instead.

Bringing up the chart to ie. Bitnami standard to allow fully changing every parameter would be a lot of work but ultimately desirable. I totally understand this may be out of scope for the chart and "users bring their your own yaml" may be preferred.

[CLAassistant]

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.

---

Pablo Moyano seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[wrenix]

the ingress is optional with loadBalancer.type="disable" ...

PS: i really dislike that schema loadBalancer instatt of ingress and type: disabled instatt of enabled: true/false. but maybe we should not create two schema for the same thing