Make client thin

Currently there is some heavy logic in client, but IMHO it is superfluous.
Instead, make client thin as possible:
* it should collect all maven config and create "seed" (ie. by hashing these things opaquely)
* based on "seed" select (or start) a daemon
* it should collect CWD and CLI params and send those those to daemon
* sit and wait, and let m39, m40, mXX decide what it likes or dislikes out of params

Start by reading the client and daemon code that handles Maven configuration, daemon selection, working directory, and CLI parameters; the issue does not name specific files or tests. Determine how the existing responsibilities are divided before estimating the refactor. Done means the client gathers configuration to identify a daemon, forwards the working directory and CLI parameters, and leaves parameter decisions to the daemon.

Written by the indexing model from the issue text.