fix: JVM truststore & keystore location

[labrenbe]

Description

The TLS secret containing truststore and keystore is mounted at /stackable/tls which is already used in Druid-specific properties (e.g. druid.auth.basic.ssl.trustStorePath). The pac4J extension uses the JVM config to configure the trust store.

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
- [ ] CRD changes approved
- [ ] 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
- [x] Code contains useful comments
- [x] 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
- [x] 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]

I have to admit I don't understand the description, could you please try to make it a bit more clear what exactly the bug is? In any case please also add a changelog entry

[sbernauer]

Closing because there are multiple different keystores, the current implementation is correct