Packaging languagetool?

Hi folks, thanks for maintaining this!

To be able to ship things built on this that work offline (once installed), I'd like to be able to encapsulate the whole dependency tree (`languagetool`, `openjdk`) as versioned conda dependencies rather than waiting for import time to download to and update `~/cache`.

Since `languagetool` could be useful outside the context of _this_ package, perhaps that should be added to `staged-recipes` (potentially built from source), and put in a well-known location (TBD) with CLI wrappers, etc.

_This_ package could then take that location into account. The existing package could become one of a few `outputs`, e.g. `language_tool_python_core`, while the new `language_tool_python` package could depend on `*_core` and `languagetool`. This _could_ be done with `preactivate` scripts (java packages often need these to up `CLASSPATH`, etc.) but a patch to `utils.py` might be more sensible.

If (some) of this sounds reasonable, I can take a whack at the `languagetool` piece!