Java security properties

[razvan]

• Added jvm module
• Added default security props.
• Fix system property value.
• Add labels to jvm security config map
• Set more labels.

Description

Please add a description here. This will become the commit message of the merge request later.

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. Integration tests passed (for non trivial changes)

Reviewer

Beta Give feedback

1. Code contains useful comments
2. (Integration-)Test cases added
3. Documentation added or updated
4. Changelog updated
5. 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

[razvan]

Feedback from @sbernauer:

• properties: HashMap<String, Option> -> properties: HashMap<String, String>
• warum nicht in rolegroup cm inkludieren?
• default nicht via serde, sondern deep merge machen
• spec.clusterConfig.jvmSecurity von Option -> XXX

[razvan]

• warum nicht in rolegroup cm inkludieren?

Non JVM products would carry a payload in CRDs that is of no use to them.

[sbernauer]

Non JVM products would carry a payload in CRDs that is of no use to them.

What I meant to say: Every product already has a rolegroup CM. In case a product is JVM based, we can add the config to the already existent CM. In case the product does not need a jvm security config, we don't need to add it to the rolegroup CM. It's the exact same thing as with e.g. a jvm config we already have

[razvan]

Java sec props are implemented as configOverrides in operators. No framework changes needed.