Clean up master branch

[AndreG-P]

Generic LaCASt Pipeline

LaCASt (i.e. the main module interpreter.lacast) will provide an API (#164) to trigger the process. It calls the submodule specific methods (interpreter.generic) to trigger MLP (interpreter.generic depends on mathosphere-core). MLP will parse the text (here wikitext) and generate tagged sentences, library of links and tex-math. Now, MLP will call LaCASt (interpreter.common) to generate a dependency graph of all math (mathosphere-core depends on interpreter.common). Based on this dependency graph and the POS-tagged text, MLP will score definiens-MOI pairs and return the graph of MOI where each node is annotated with the definiens and the corresponding score. This graph goes back to interpreter.generic which now replaces generic LaTeX with semantic LaTeX based on the annotated graph of MOI. After that, the results go back to LaCASt main (interpreter.lacast) which now translates the semantic LaTeX to CAS.

Once Mathosphere is Deployed

During the development of the generic latex extension, LaCASt depends on mathosphere. Since we update mathosphere regularly also, LaCASt depends on the not published SNAPSHOT version of mathosphere. To keep track of these changes, I added mathosphere as a submodule and LaCASt has mathosphere as a mvn submodules.

Hence, a maven install also installs mathosphere now (completely). We will skip the tests in mathosphere to save compilation time. Once we finished the development, it makes sense to deploy the new version of mathosphere (mvn central) and remove the submodule dependency here.

It will not be merged to master. We develop in wikipedia-branch.