Allow specifying additional extensions to load in Druid

[labrenbe]

Description

Closes #490

Currently the only way to enable additional extensions is to use config overrides potentially removing extension that were added to the extension load based by the operator

This PR adds a field additionalExtensions to clusterConfig containing a simple list of extension names. Extra configuration required by additional extensions is not in scope of this PR.

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

# Author
- [ ] Changes are OpenShift compatible
- [X] CRD changes approved
- [X] CRD documentation for all fields, following the [style guide](https://docs.stackable.tech/home/nightly/contributor/docs-style-guide).
- [ ] Helm chart can be installed and deployed operator works
- [ ] Integration tests passed (for non trivial changes)
- [ ] Changes need to be "offline" compatible

# Reviewer
- [ ] Code contains useful comments
- [ ] Code contains useful logging statements
- [ ] (Integration-)Test cases added
- [ ] Documentation added or updated. Follows the [style guide](https://docs.stackable.tech/home/nightly/contributor/docs-style-guide).
- [ ] Changelog updated
- [ ] Cargo.toml only contains references to git tags (not specific commits or branches)

# Acceptance
- [ ] Feature Tracker has been updated
- [ ] Proper release label has been added
- [ ] [Roadmap](https://github.com/orgs/stackabletech/projects/25/views/1) has been updated

[sbernauer]

As talked offline I pushed the experiment to feat/additional-extensions-review.
We also created kube-rs/kube#1484

[sbernauer]

Otherwise LGTM

[sbernauer]

Many thanks!