chore(chart-deps): update ingress-nginx to version 4.13.1

[svcAPLBot]

This PR updates the dependency ingress-nginx to version 4.13.1.

It also includes a number of changes, partially as a cleanup and for compatibility:

• Many commented configuration lines, upstream defaults, and deprecated (or otherwise non-functional) options were removed.
• The controller scope was extended to its own namespace (using label selector), as errors were logged accordingly even before this upgrade.
• proxy-busy-buffers-size was added to override the default. The value needs to be >= proxy-buffer-size which we have increased.
• Log verbosity was tuned down as this was not any helpful.
• OpenTelemetry is no longer a sidecar, but the module is included already.
• Snippets within the Ingress resource are considered a security risk with rating Critical (https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations-risk/) and only permitted after setting configuration options to disable checks. It has turned out that existing snippets were either ineffective due to configuration errors, or in case of OAuth2-Proxy no longer necessary.

[CasLubbers]

Tested on cluster created workloads with some services and all worked. Couldn't find regression ✅

[CasLubbers]

I was a bit to soon with my approval. When I press log-out. It redirects to:
https://auth.caslubbers-1.dev-akamai-apl.net/oauth2/start?rd=https://console.caslubbers-1.dev-akamai-apl.net%2Fapps%2Fadmin
And I see:
default backend - 404
This was on a cluster that was on main and then upgraded to this branch

edit: it keeps redirecting to that page so I cannot log back and I am basically stuck

[merll]

I was a bit to soon with my approval. When I press log-out. It redirects to: https://auth.caslubbers-1.dev-akamai-apl.net/oauth2/start?rd=https://console.caslubbers-1.dev-akamai-apl.net%2Fapps%2Fadmin And I see: default backend - 404 This was on a cluster that was on main and then upgraded to this branch

edit: it keeps redirecting to that page so I cannot log back and I am basically stuck

Tested different approaches to fix this, and added a post-upgrade script to run Helmfile with that one ingress that does not get updated.

[CasLubbers]

Tested upgrade on cluster again and worked without issue

[Ani1357]

Tested again and now it works as expected.