feat: move patch apply logic to patchable

[dervoeti]

Description

This is a draft PR to solve #677. I replaced the apply_patches.sh script with Patchable for Zookeeper and Druid.

We decided in https://github.com/stackabletech/decisions/issues/44 that all sources should be mirrored on Github (to be implemented by #1011).

My idea was that we can just reuse the existing checkout logic, since it does exactly what we want: checkout a repo at a specific commit and apply a bunch of .patch files on top of it. In this PR, the original Apache repositories are used, those would need to be replaced by our mirror repos.

I added an optional flag --images_repo_root to manually specify a custom root for the images repo instead of relying on the auto-detection that Patchable currently does. We could also just use the auto-detection, but then we'd probably need to run git init && touch .patchable before running the patchable checkout command inside the container, which is a bit awkward. The extra flag isn't super pretty either though and I couldn't get around using PathBuf in the implementation, hence I made this a draft PR to serve as a PoC. This is just one way we could replace the patch scripts with Patchable. Maybe this can be solved in a more elegant way, I didn't find one yet though.

Definition of Done Checklist

• Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
• Please make sure all these things are done and tick the boxes

Tasks

Preview Give feedback

1. Changes are OpenShift compatible
2. All added packages (via microdnf or otherwise) have a comment on why they are added
3. Things not downloaded from Red Hat repositories should be mirrored in the Stackable repository and downloaded from there
4. All packages should have (if available) signatures/hashes verified
5. Add an entry to the CHANGELOG.md file
6. 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:

bake --product <product> --image-version <stackable-image-version>
kind load docker-image <image-tagged-with-the-major-version> --name=<name-of-your-test-cluster>

See the output of bake to retrieve the image tag for <image-tagged-with-the-major-version>.

[nightkr]

I assume this is an earlier revision? I think I prefer how it's done in druid

[dervoeti]

I think it was done this way to copy both the JMX config and the patches in one line, but I aligned it now, so we have the same patch directory structure everywhere.

[dervoeti]

@nightkr It's ready for another round of feedback 🙂 Once it's in a good shape I'll start adapting the patch processes of the other products.

[nightkr]

Largely LGTM

[dervoeti]

@nightkr I migrated all Dockerfiles now and tested all builds using the latest versions of the product, worked fine.