Intersmash should run with products and not just with community projects

[fabiobrz]

Is your feature request related to a problem? Please describe.
Intersmah should be able to run with products' bits and deliverables that originate from the currently supported community projects (e.g.: WildFLy -> EAP, Keycloak -> RHSSO etc.)

Describe the solution you'd like
When using Intersmash for provisioning an interoperability testing scenario, users should be able to use products' bits and deliverables (e.g.: images) for configuring what actually would be provisioned.
This means that the provisioning components should be validated with such configured values.
This should be done by adding/modifying tests to the testsuite module, as it has been done in #21.
BTW - this affects the deployments module, which is used by some provisioners, namely the WildFly one. Such deployments are currently built with community artifacts, while they should use productized ones when the tests involve products rather than community projects. This could be done by defining a dedicated Maven profile to cover the differences in configuration.
Given the provisioners will try to use images which are available from a non-public registry, the Intersmash OpenShift CI infra configuration will be modified as needed, e.g.: for storing the secrets to access such registries.

Describe alternatives you've considered
None, this is a required feature for being able and use Intersmash for provisioning and test scenarios with products rather than community projects.

Additional context
N/A

[fabiobrz]

Starting with openshift/release#41412 in order to experiment with pull-secret for secured registries. When ready to start the rehearsal job it would run the changes in the following topic branch: https://github.com/Intersmash/intersmash/tree/testps (see 4545c3b)

[fabiobrz]

openshift/release#41412 is now merged, therefore we can start playing with Intersmash OpenShift e2e test script to experiment/test with it.