Unify Kogito Quarkus and Spring Images

As a user I would like to build or deploy a kogito service without need to care about what builder and runtime image I'll be using to regardless of the runtime, Quarkus or Springboot.

Today we have 2 builders and 3 runtime images.

• Quarkus s2i
• Quarkus JVM runtime
• Quarkus runtime for native builds
• Springboot s2i
• Springboot JVM runtime

The builders and runtime ones can be unified.

Operator and CLI changes should be handled as part of this jira.

Resulting images:

s2i image to handle: Quakus JVM, Quarkus Native, Springboot

Native runtime for Quarkus

Java runtime for Quarkus JVM and Springboot