TEIIDDES-2147: Updates library versions of teiid client dependencies

* Adds in additional netty library dependency required for war creation
TEIIDDES-2157 Changed deleteMarkers() calls to use DEPTH_ZERO instead of DEPTH_INFINITE
TEIIDDES-2127 Problem with SF import using Teiid Connection importer - keys not resolved
Merge pull request #344 from phantomjinx/TEIIDDES-2147

TEIIDDES-2147: Updates library versions of teiid client dependencies
Merge pull request #345 from mdrillin/TEIIDDES2127

TEIIDDES-2127 Problem with SF import using Teiid Connection importer - keys not resolved
TEIIDDES-2120: Fixes for Vdb and VdbEditor

* VdbEditor
 * Fixes when user files are added to a vdb. Formerly, the absolute path of the
   file was supplied to the VdbEntry even if it was in the project. Consequently,
   these files would never synchronize as they were not model resources and their
   paths could not be found in the workspace.

* VdbEntry
 * Makes the findFileInWorkspace method work a little harder to try and locate a
   resource for the given filename by navigating the files container in the vdb's
   project. This improves the chances that such files can be synchronized.

* Vdb
 * Stops udf jar files appearing in both the UDF and Other Files panels in the
   VdbEditor. Only user files should appear in the userFileEntries set.

Conflicts:
	plugins/org.teiid.designer.vdb.ui/src/org/teiid/designer/vdb/ui/editor/VdbEditor.java
	plugins/org.teiid.designer.vdb/src/org/teiid/designer/vdb/VdbEntry.java
TEIIDDES-2156: Ensures eclipse builder is not stopped by runtime exceptions

* Executing an unreliable operation in OperationUtil can throw an exception
  Previously this was a runtime exception which stops the eclipse builder
  dead in its tracks.

* Fixes this issue by throwing a normal exception and ensuring that all
  clients properly handle the exception by exposing it to the user in some
  form of dialog.

* ErrorHandler
 * Catch-all for taking an exception and displaying it in the eclipse
   built-in error dialog.

* Where methods and functions are low-level, the exception is simply thrown

* Only when the class appears at the UI layer is the exception handled and
  displayed.

* VdbEditor
 * Since this is a UI editor, a correctly initialised Vdb is vital. Since
   the latter depends on OperationUtil, display an informative error panel
   if the editor's Vdb instance cannot be created.



* Test
 * GenerateRestWarDialog
 * Rename of vdb, model resource
 * DDLImporter
 * Deploy Vdb action
 * Execute Vdb action from runtime/ui/actions
 * Execute Vdb action from runtime/ui/vdb
 * GenerateRestWarAction
 * TeiidServerEditor initialising editor
 * VdbExtractModelsSyncVdbMarkerResolution
 * VdbModelPathResolution
 * VdbEditor
  ** save
  ** add model
  ** update UDF jars
  ** add udf jar