Don't build an IntegrationKit on upgrade with same runtime version

[squakez]

When we upgrade from one operator version to another and after the user execute a rebuild (ie, kamel rebuild) a new IntegrationKit is created, likely because we consider the new operator version. This happens also when we don't change the default runtime version. I think we can avoid to build a new IntegrationKit at all, however, the problem is that, even building the new IntegrationKit, then, this is not picked by the new Integration run (which uses the previous one). Probably this is happening because we don't check the operator version when looking up for kits, but only the runtime version.