Store integration code in a configmap

[lburgazzoli]

We do store the integration code inside the Integration CRD but it would be better to have a default strategy that stores it in a configmap and mount them to the runtime pod

[nicolaferraro]

I was thinking to keep the CR self contained as much as possible. We can use the configmap strategy as mechanism to put the code into the pod. In this scenario, the configmap is created by the operator to inject the code. The user updates the CR, the operator reflects the changes into the configmap, then refreshes the deployment.

[nicolaferraro]

We are talking here about a technical configmap.

There'll be cases where we want to let users externalize configuration in configmaps and secrets, but that is a different story.