Fix Kafka SSL scenarios in FIPS enabled environment by regenerating certs

[michalvavrik]

Summary

We have in place default p12 keystore for Strimzi vendor that has certs generated with algorithm not supported in FIPS. I can't just override it in tests because they all are expecting one truststore. I have decided to re-generate them and refactor it bit to avoid repetition. It's quite quick.

Sadly, this doesn't fix SASL_SSL scenarios as plain auth mechanism just doesn't work in FIPS. I don't know what to do about that part and in the future there will be follow-up, but this PR will help to to fix SSL scenarios at least.

I am adding support for Docker host porting to localhost that we use for Kafka SSL scenarios to also drop repetition.

This PR should be backwards compatible and should not break anything, I run couple of Kafka modules in TS with it.

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]

run tests

[michalvavrik]

run tests

[mjurc]

run tests

[mjurc]

Besides the one nit, I don't see anything wrong about this. Let's see about the CI.

[michalvavrik]

OC jobs are failing but it's not connected to this PR judging by logs. AFAICT I didn't touch anything related to OCP, they have their own builder.

[mjurc]

Thanks for your efforts.