HPCC-JAPIs-29 migration

Migration and integration of HPCC WS logic currently used in org.hpccsystems.eclide.

- The project is structured in abstract layers
 - org.hpccsystems.ws.client/org.hpccsystems.ws.client.gen.<wsname>.vX_Y (Soap Stub generated logic)
 - added wsdl ver to package name (not the greatest version control, but will keep it manageable as new versions are introduced)
 - generated via Eclipse Web Service Client wizard, which includes convenient soapproxy classes.
 - org.hpccsystems.ws.client/org.hpccsystems.ws.client
- Interface through the HPCCWSClient, it provides connectivity logic, ws client management, and high level WS action support
- Each ESP Web service supported has its own client, the client encapsulates all information pertinent to the Web Service 
- Provides higher level actions related to the WS (ie, exposes helper methods that make multiple WS calls, etc.)
- Helper methods are added as need arises
- org.hpccsystems.ws.client/org.hpccsystems.ws.client.platform
                - This set of classes represent the platform and its units
                - Mostly migrated from your project org.hpccsystems.eclsoap/org.hpccsystems.esp
                - Most connectivity/WS interaction abstracted out
                                - Some refactoring done to fit project structure, but for most part you should be able to use without major code changes
                - org.hpccsystems.ws.client/org.hpccsystems.ws.client.utils
                                - Exposes reusable logic (I am actually considering moving some of this logic to its own project since its generic and can be used by other projects)
                                - Encapsulates all connection information and exposes many helper methods (heavily used by ws.client package)
                                - DatasetParser is still used, but take a look at Utils.parseECLResults(String results) –builds a DOM and performs tree based parsing
                                - StackHandler and HashCodeUtil – are these homebrews? If not, are we legally allowed to publish?
                                - DelimitedDataOptions represents our delimited data requests parameters
                                - FileFormat – enumerates all our known/supported file types, and provides fast enumeration to human readable conversion
                                - Utils – catch all class, some of the features currently housed here could/should move 

- Eclipse project files are provided (convenient for eclipse developers, but might remove since the project has been “mavenized”
- Maven build mechanism included which allows us to automate the build and packaging into basic jar, or self-sufficient jar (dependencies included)

- HPCC-JAPis repo contains other projects as well:
                - org.hpccsystems.ws.client.legacy/
                                -separate project meant to house similar support for esp services no longer provided/supported by OSS HPCC

                - org.hpccsystems.clienttools/
                                - Will contain java interface to various HPCC client tools 
                                - Currently only interfaces to ECLCC (this code was contributed)
                                - We can grow this project as need arises

Signed-off-by: rpastrana <rodrigo.pastrana@lexisnexis.com>