Add support for encrypting PKCS#12 stores with a password

[nightkr]

Description

Fixes #313.

We add a new volume parameter secrets.stackable.tech/format.compatibility.tls-pkcs12.password for controlling this. The password should not be considered private (PVC manifests are generally public!), this is purely for compatibility with certain broken apps.

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

Beta Give feedback

1. Changes are OpenShift compatible
2. CRD changes approved
3. Helm chart can be installed and deployed operator works
4. Integration tests passed (for non trivial changes)

Reviewer

Beta Give feedback

1. Code contains useful comments
2. Changelog updated
3. Cargo.toml only contains references to git tags (not specific commits or branches)

Acceptance

Beta Give feedback

1. Feature Tracker has been updated
2. Proper release label has been added

[nightkr]

I'm not sure if this is something that we want to document, since this is more of a desperate "feature of last resort".

[maltesander]

LGTM! Lets wait what the arch meeting brings.

[siegfriedweber]

In general okay after the comment for compat_tls_pkcs12_password is fixed.

I would not emphasize it so much that the password is used for compatibility reasons. It is an option (and not a compatibility option) which is used for compatibility and not too useful on its own.

[nightkr]

It only exists for compatibility, and provides no useful security improvement on its own.

I absolutely want to avoid misleading people around this...

[siegfriedweber]

LGTM