True TRAMP Support

#1559 (and accompanying #1739) suppose that compilation may be done over TRAMP, however `haskell-interaction-mode` still appears to use a local ghci. (which, for example, the less feature-full `run-haskell` does not).
Use cases for interactive haskell development over TRAMP include:

- Development in a container (such as with tramp-nspawn or docker-tramp) without running emacs _within_ the container.
- Development with more powerful (or specialized) hardware over ssh, without resorting to `emacs -nw` or X11 forwarding.

I understand that this should be considered a feature request, and it is something I will be looking into myself (although my skills with elisp are not advanced).

Start by reading the haskell-interaction-mode entry points and comparing their process handling with run-haskell. Review issues #1559 and #1739 for the existing compilation-over-TRAMP context. Done means interactive Haskell development uses the remote environment over TRAMP rather than a local ghci.

Written by the indexing model from the issue text.