Backport of builtin/k8s: Introduce Ingress resource support for Kubernetes Releaser into release/0.5.x

[hc-github-team-waypoint]

Backport

This PR is auto-generated from #2261 to be assessed for backporting due to the inclusion of the label backport/0.5.x.

WARNING automatic cherry-pick of commits failed. Commits will require human attention.

The below text is copied from the body of the original PR.

---

This pull request adds a new config option ingress within the Kubernetes release manager that allows users to have their releases be configured behind an ingress resource that accepts traffic from an ingress controller in their cluster.

Fixes #889

This doesn't have to be gated to 0.6.0, it can be released with the next minor.

Some example apps:

• k8s/ingress: Add an ingress release example waypoint-examples#77
• k8s/ingress: Add a multi application project that releases with Ingress resources waypoint-examples#78

[hashicorp-cla]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

---

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.

_{Have you signed the CLA already but the status is still pending? Recheck it.}

[briancain]

Closing for #2311