chore(druid): Update major/minor versions for 26.11.0

Inizia con boil-config.toml e con le directory esistenti delle versioni e delle patch di Druid; confrontale con le versioni concordate e rimuovi le voci obsolete. Controlla quindi druid-opa-authorizer, operator getting_started/kuttl/supported-versions, demos e required-external-components.adoc, usando i comandi boil build e smoke-test elencati. Il lavoro è completo quando l’immagine viene compilata, i test applicabili hanno esito positivo e vengono aggiunti tutti i link correlati alle note di rilascio e alle pull request.

Part of https://github.com/stackabletech/docker-images/issues/1641.

• Remove: 30.0.1, 35.0.1

[!TIP]
Please add to the Stackable Engineering project.

Update tasks

• Update the druid-opa-authorizer with the new set of versions (profiles).
• Release a new version of druid-opa-authorizer, if compiling against the new Druid version(s) requires changes in the code.
• Update boil-config.toml to reflect the agreed upon versions in the spreadsheet (including the removal of old versions).
• Update boil-config.toml to the latest supported version of JVM (base and devel).
• Update boil-config.toml to the latest supported version of Hadoop.
• Initialize new product versions with patchable and add patches if applicable.
• Delete old patch directories.
• Check the corresponding operator (getting_started / kuttl / supported-versions) for usage of the versions.
• Check other operators (getting_started / kuttl / supported-versions) for usage of the versions. Add the PR(s) to the list below.
• Ensure prerequisites are up to date (required-external-components.adoc).
• Update the version in demos. Add the PR(s) to the list below.

Related Pull Requests

[!TIP]
Delete any items that do not apply so that all applicable items can be checked.
For example, if you add release notes to the documentation repository, you do not need the latter two criteria.

• Link to druid-opa-authorizer PR
• Link to the docker-images PR (product update)
• Link to the operator PR (getting_started / kuttl / supported-versions)
• Link to any other operator PRs (getting_started / kuttl)
• Link to demo PR (raise against the main branch)
• Link to the Release Notes PR in the documentation repo (if not a comment below)

Acceptance

[!TIP]
This list should be completed by the assignee(s), once respective PRs have been merged. Once all items have been
checked, the issue can be moved into Development: Done.

• Can build image (either locally, or in CI)
• All kuttl tests pass (either locally, or in CI)
• Release notes added to documentation and linked as a PR above
• Release notes written in a comment below
• Applicable release-note label added to this issue

# Where x.y.z is the new version added in this PR
boil build druid=x.y.z --strip-architecture --load

kind load docker-image oci.stackable.tech/sdp/druid:x.y.z-stackable0.0.0-dev

# Change directory into the druid-operator repository and update the
# product version in tests/test-definition.yaml
./scripts/run-tests --test-suite smoke-latest # or similar

Please consider updating this template if these instructions are wrong, or
could be made clearer.