Update the readme

* Point to the up-to-date setting up article as current instructions are
  out-of-date and its crazy to have instructions in 2 different places.
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.
TEIIDDES-879: Actually make use of the jar in the connection JAR_LIST

* The connection class was modified to fetch the teiid driver using the
  roundabout route of finding the client runtime plugin supported by the
  version specified then loading its driver.

* However, the classloader provided is created from the jar list defined
  in the DTP driver instance configuration and as such should already
  contain the most appropriate driver, especially as the list is now
  auto-created by default.

* Use the driver from the classloader first and only if that fails resort
  to the more circuitous route of obtaining a driver.
TEIIDDES-1322: Adds url properties text box to Teiid connection wizard page

* Adds a freeform textbox to allow url properties to be appended to the
  teiid connection url. It suggests that the string should be in the
  correct format but does not check it to allow the user the freedom to
  insert custom properties. The finished url is obvious so if the user has
  entered it incorrectly then it should be obvious.

* Support for url properties is already part of the TeiidServerJDBCURL
  class. Small fix required in latter class when using url properties.
TEIIDDES-1738 changed existing object check to use relative model path rather than URI
teiiddes-1633: Added check...  if tns in XSDFeature is null, then check the XSDComplexTypeDefinitionImpl instance.
Merge pull request #188 from tejones/teiiddes-1633

teiiddes-1633:
TEIIDDES-879: Surround loading of class with exception handling

* If the classloader fails to load the class, avoid letting an exception
  thrown so that the version can be found using the runtime client
  registry.

* This mitigates the possibility that users still have the original
  default Teiid driver instance.