daemon.js: --xp-mode tries to allocate a server with no free RAM for hacking

[alainbryden]

I suspect that on occasion, targets are re-allocated to a new server which is still running hack scripts for another server, and then complains when there's no ram free on that server for scheduling:

It's not a huge deal and it will eventually have free ram, so we should perhaps quiet these notifications, but I should get to the bottom of this and come up with a more reliable way for allocating targets to servers (or just save "allocation" logic for --looping-mode).

Perhaps, the current behaviour (sort servers by max ram, then allocate) should be kept for --looping-mode, but normal --xp-mode which does things a bit more on-demand should just sort servers by available ram, and/or keep better track of which targets are currently have batches running on servers, and exclude them from the current loop until they're done.