[sonataflow-operator] Provide a tagging mechanism to know in which operator version a managed k8s object was created

[wmedvede]

We must analyze/research, the convenience of a solution that somehow tag the k8s objects created/managed by the operator, to know in which operator version they where generated.

Could this be helpful to know in future operator versions, the set of changes that must be applied given that an k8s object was generated in the operator version 1.2.3, and we are now, in the version 1.4.5. ?

We must see the pros / cons of such solution, and implement if we can get real value.

Implementaion notes: the mechanism could be as simple as decorating the generated k8s objects with convenient annotation.
Double check the sonataflow.org//operator.id annotation.