Support OCP secrets with destination mount path

[michalvavrik]

Summary

From user POV it's same as we already support for resources (config maps), I just wrote it slightly differently. Keycloak image has only certain dirs writable so I need to specify destination, but for certs can't use config maps as binary data needs to be base64 encoded as secrets do. I've tested it on what I am preparing for mTLS OIDC test (not that I'm done, but Keycloak starts with keystores and truststores).

Please check the relevant options

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Dependency update
• Refactoring
• Breaking change (fix or feature that would cause existing functionality to change)
• This change requires a documentation update
• This change requires execution against OCP (use run tests phrase in comment)

Checklist:

• Example scenarios has been updated / added
• Methods and classes used in PR scenarios are meaningful
• Commits are well encapsulated and follow the best practices

[michalvavrik]

run tests

[michalvavrik]

GH CI failures go down to the #991, luckily this PR changes can affect only OCP and nothing else. Let's pay attention to OCP CI please.

[jedla97]

LGTM! Looking at CI all is green so merging.