Research to remove supporting Kogito Services CRD

Right now we have too many supporting services controllers and Kubernetes Custom Resources being managed by the operator. They are much look alike, the deployment interface does not have too many differences between them, which do not justify one controller for each one.

This proposal is to have one unique CRD to deploy any support services that will receive the `type`, `image` and other agnostic attributes. One controller will be responsible to coordinate the deployment process according to this interface, thus removing KogitoDataIndex, KogitoMgmtConsole, KogitoJobService and so on