fix(trino): Backport airlift/airlift#1943 for max response header size

[dervoeti]

Description

Backport airlift/airlift#1943 into the Airlift dependency shipped with Trino, so Jetty actually honours the configured max response header size (calls setMaxResponseHeaderSize in addition to setResponseHeaderSize).

To do that, a new trino/airlift image is added that builds Airlift from source and applies the patch. The existing trino/trino build then uses this patched Airlift instead of the original dependency.

Two Airlift versions are patched, matching what Trino expects:

• Airlift 361 for Trino 477
• Airlift 386 for Trino 479

Once airlift/airlift#1943 is merged and Trino picks up a new Airlift release that contains the fix, the entire trino/airlift directory and the airlift-builder stage in trino/trino/Dockerfile can be removed again.

Smoke test passes:

--- PASS: kuttl (586.26s)
    --- PASS: kuttl/harness (0.00s)
        --- PASS: kuttl/harness/smoke_trino-477,oci.stackable.tech_sandbox_trino_477-stackable0.0.0-dev-amd64_hive-4.2.0_opa-1.12.3_hdfs-3.4.2_zookeeper-3.9.4_openshift-false (586.22s)

Definition of Done Checklist

• Changes are OpenShift compatible
• All added packages (via microdnf or otherwise) have a comment on why they are added
• Things not downloaded from Red Hat repositories should be mirrored in the Stackable repository and downloaded from there
• All packages should have (if available) signatures/hashes verified
• Add an entry to the CHANGELOG.md file
• Integration tests ran successfully

TIP: Running integration tests with a new product image

The image can be built and uploaded to the kind cluster with the following commands:

boil build <IMAGE> --image-version <RELEASE_VERSION> --strip-architecture --load
kind load docker-image <MANIFEST_URI> --name=<name-of-your-test-cluster>

See the output of boil to retrieve the image manifest URI for <MANIFEST_URI>.

[sbernauer]

There was an upstream review, which is great! I would suggest to wait with merging this until the upstream PR is merged or sufficient time is passed without review feedback.
Just that we don't e.g. introduce new bugs are take a performance hit.

[dervoeti]

@sbernauer The patch has been merged upstream, I updated the patch here so it also includes the MaxDataSize annotation that I added in the upstream PR.

[sbernauer]

There was an ask for a test upstream, I let you decide if you want to wait with merge until we figured that out