extracting java API

[renepickhardt]

making a clearer cut between tomcat and java API such that graphity can be extracted as a jar file and tomcat is only handling the REST part and the protocol syntax checking and the rest is done by the graphity libs which could be running in embedded mode... The java API should be conform to the REST API. The jars should handle the synchronization of the algorithm and not the tomcat. If synchronization is possible to be solved via neo4j transactionmanagement then this should be done.

Finally the tomcat REST Server should only include graphity.jar via maven and wrap it.

this issue is related to #1 since especially for the write optimized algorithm synchronization will probably not be necessary.