TEIIDDDES-879: Remove designer.core dependency from datatools.connectivity

* The datatools.connectivity bundles should be at the foot of the plugin
  dependency tree and should not depend on the designer.core plugin.

* Since the plugin also lives in a different feature, it makes sense to
  avoid this cross-dependency.

* ConnectivityUtil
 * Since the TeiidJDBCConnection is the only class that requires the
   getTeiidDriver() method, it is better to locate it here.
TEIIDDES-879: Migrate driver template to teiid runtime plugins

* Migrates the common Teiid driver template defined in the connectivity
  plugins and moves the version-related parts down to the runtime plugins
  so that 3 versions of the driver template and default instances will be
  available to the user.

* The advantage is that the runtimes themselves become the driver jars so
  users have no need to specify the jar to use as the sql driver.
TEIIDDES-879: Ensure the feature dependencies are correct

* The teiid runtime client plugins now depend on the connectivity plugins
  and as such that feature must be included in the client feature when
  installing.

* The main designer feature does not include the connectivity feature either
  so its a miracle that no errors have been reported when this has not
  been installed, since it depends on at least connecitivity.ui

* Likewise the connectivity feature must include the spi since it is relied
  upon by the plugins. Its never been a problem before since all 3 features
  are installed together so the spi has been present. However, installing
  the connectivity feature on its own will fail due to the lack of the spi
  plugin.
TEIIDDES-879: Updates client runtimes

* Repoint to the sub-module commits that provide the individual driver
  definition implementations.