Malformed config files cause catastrophic failure

[bbenligiray]

I SSH'd to a machine, started a hinter-core container, tried to add a peer manually, during which I may have saved an invalid hinter.config.json file. I lost connection and failed to connect again. Created another instance, went through the same steps, same thing happened. Needs to be investigated.

[bbenligiray]

A similar issue: deleted a peer-specific hinter.config.json while hinter-core was parsing peers, it crashed and pm2 failed to restart the process. Error handling is omitted because such issues are intended to be resolved automatically through restarts, so it needs to be investigated why this is not working.

[bbenligiray]

fixes the periodic peer config check (that detects config changes). It wasn't detecting changes because it used peer.toString() on the object (which always produces '[object Object]'). It now uses JSON.stringify(peer)

from #84 (comment) may be related