The node will sometimes not automatically reconnect correctly if connection fails/disconnection occurs

[nagisa]

I am seeing sometimes that the node provided by this project is stuck in "disconnected" state. I was not able to catch a moment to debug this quite yet, however.

But from a brief code review, I think I can see a few reasons why this may be happening:

1. mowerConnection.getMowers() throws an exception → the connect method will terminate prematurely and not schedule a repeat attempt to connect;
2. mowerConnection.activateRealtimeUpdates() throws an exception → similar outcome;
3. Within automower-connect library itself, if checkClose fires, it will move on to re-establish the connection, but if this attempt throws an exception the loop to maintain a live websocket connection gets broken.

I believe solving 1 and 2 will largely solve 3 implicitly, but it may make sense to address all of these independently.