Allow Outpost configuration to overwrite tls hosts for kubernetes integration

**Is your feature request related to a problem? Please describe.**
Authentik Outpost with Kubernetes integration creates one TLS-Host entry for each application active in the Outpost, when using cert-manager you can create certificate requests automatically, it would be great to have the option to overwrite this behaviour with wildcard certificates. I think it would be more economical to request a couple of wildcard certificates for the outpost instead of requesting a named certificate for each application behind authentik.

**Describe the solution you'd like**
I´d like to have an additional Outpost configuration option containing a list of hosts:
```
kubernetes_ingress_tls_hosts:
- *.example.com
- example.com
- *.foo.com
- foo.com
```
This would allow cert-manager to create less letsencrypt certificates and allows excluding entries.

**Describe alternatives you've considered**
An alternative would be to manually request the certificate using cert-manager and assigning the tls-secret in authentik.

**Additional context**
Here is a quick example how many hosts are in my outpost, and this is just my small lab. :)