Idiomatic way of handling daemon and client

[schrieveslaach]

@blinry reported in ethersync/ethersync#257 somethings that should be considered as input to decide which is the best way of handling the daemon and client:

• Starting the daemon from within Intellij, it uses a --socket-name ethersync-playground-socket, which was unexpected – at first, I tried to use the default socket with another editor. The socket is our workaround for having more than one Ethersync daemon at a time – in the long term, we might add multi-project support to the daemon. But in this plugin, it might make sense to use the default socket.
• Is there a way to stop the daemon spawned by Intellij?
• Say I wanted to follow the current "standard model", where one launches the daemon on its own, outside of any editor. Could I currently do it using the plugin?
• It sometimes makes sense to use Ethersync with a password, so others in the same network can't join. We use the configuration files to store them. I wonder how this feature could be smoothly integrated into the current plugin. Again, I feel a bit uneasy about integrating the daemon launch into the plugin, because I expect it will change quite a bit. In our thinking so far, ethersync daemon is not part of the "editor interface", instead, ethersync client and the editor sync protocol is. (For the daemon, we might switch to an ethersync share/ethersync join interface at some point). But I get your reasoning that people might expect such a functionality. I'm happy about experimenting on this front, and finding the best solutions!