Manage CI/CD for DV in Syndesis

We need to align with the CI/CD feature of syndesis. That is support tagging virtualizations with environment names, then providing service methods for import/export based upon the environment name and tracking of migrations.

Essentially this is handled in syndesis via https://github.com/syndesisio/syndesis/blob/ed1323553e58d833d12350456fb425933ed99184/app/server/endpoint/src/main/java/io/syndesis/server/endpoint/v1/handler/external/PublicApiHandler.java along with some tracking information stored on the integration.

Their logic also handles the import/export of connections, which TEIIDTOOLS-728 does not. See the parent issue TEIIDTOOLS-728 for more on details. The summary is effectively:

If they are open to us sharing this feature, then we will spawn some issues and determine who can do the work. Essentially we'd update their logic to handle virtualizations - which in part would need to use our service methods to find/export virtualizations. There are probably two approaches. Either introduce an integration into syndesis that represents a virtualization when a virtualization is created (it would need some kind of flag that they could otherwise filter it out) - and on our side update it appropriately based upon its lifecycle, or at least their public api will need to be wired even more significantly into our api - and we'd need to track more state (note that ContinuousDeliveryEnvironment for example is stored on the integration).

If they are not open to this, then we have to develop a parallel feature.