[ENHANCEMENT] Align response-header-size options and bump it higher

[jessesimpson36]

Describe the use case:

It's been pretty common that we've heard of people running into issues when they try to log in, and the token in the response header is so large that it exceeds the max size of the buffer. There are application-side reasons that this can occur, such as a web component having a default value. But there is also the ingress-side configuration which often appears as a 500 without a stacktrace.

These configuration options should be unified, and we should make sure this option is sufficiently large.

Currently, the options for the ingress is

      nginx.ingress.kubernetes.io/proxy-buffer-size: '128k'

And the option for the web components is the default 8KB for Jetty:
https://docs.spring.io/spring-boot/appendix/application-properties/index.html#application-properties.server.server.jetty.max-http-response-header-size

server.jetty.max-http-response-header-size

The following should be the env variable representation:
SERVER_JETTY_MAX_HTTP_RESPONSE_HEADER_SIZE

However, it's important to note that Optimize sets this value explicitly and uses their own variable for it. I'll try to find a link to it.
https://github.com/camunda/camunda/blob/56febdfddd5cf8012b919d668ed889287255edc0/optimize/util/optimize-commons/src/main/resources/service-config.yaml#L130

CAMUNDA_OPTIMIZE_CONTAINER_MAX_RESPONSE_HEADER_SIZE_BYTES

Describe the enhancement/feature:

Desired outcome and acceptance tests:

[jonathanlukas]

The env for optimize would be:

CAMUNDA_OPTIMIZE_CONTAINER_MAX_RESPONSE_HEADER_SIZE_BYTES = 32768