Make it easier to discover all CRDs

[scholzj]

trafficstars

We should make it easier to discover all of our CRD. Currently, in the api module, we have already some methods which provide the CRD Java classes (e.g. the CRDS array). But it is not easy to use, because it provides only the class. It does not provide the CRD YAMLs, the List classes etc. For example the YAML is only provided via a field in the test module out of the packaging directory. This is also causing a bit of a dependency mess.

It would be nice to have some methods which would provide all the needed resources to work with / crete the CRDs. All Java classes but also the definition YAMLs (or paths to them). We should have them in one easy to use module. Either in the api module or for example in some new crd module. The definition YAMLs might be packed as resources so that it can be used as maven dependency otisde the Strimzi installation folder or even online to for example check whether the resources installed in cluster are up to date etc.

This was rased in #6727 (see this discussion). The MockKube2 might be one of the first usecases for this -> to automatically install all the CRDs when initiailized.

[scholzj]

Triaged on 7.6.2022: Should be kept open. Help wanted.