Move Java (codelens, hover) support in new a language server

[angelozerr]

Today MicroProfile LS manages properties and java files both. It means that all client capability are shared between those 2 language. For instance, the format support is available for properties files but not for java files.

It causes this issue redhat-developer/vscode-quarkus#166

The Java support are done for CodeLens and Hover and doesn't use the MicroProfileProjectInfo, it means properties and java support shares anything, so we could move the java support in an another language server.

[angelozerr]

I close this issue because:

It causes this issue redhat-developer/vscode-quarkus#166 -

It was fixed

The Java support are done for CodeLens and Hover and doesn't use the MicroProfileProjectInfo, it means properties and java support shares anything, so we could move the java support in an another language server.

In Java files context we use application.properties from target, classes (and not sources) to provide in hover, code lens URL values which could be replaced by maven process, which is better.