Lakeshore240 agents should not quit the acq process when disconnected

[jlashner]

Currently if a lakeshore240 loses connection, the ls240 module object loses connection, and the acq process crashes. It is currently impossible to re-initialize the object with the initialize task, since the agent will think it's already initialized and exit out:

socs/socs/agents/lakeshore240/agent.py

Lines 58 to 59 in 593ce9d

	if self.initialized:
	return True, "Already Initialized Module"

I think we should make the changes I made to the vantage agent here (https://github.com/simonsobs/socs/pull/524/files), and have it so that if daq times out in the acq process, instead of crashing, it attempts to re-connect, and then waits for 30s or so. That way when it's plugged back in it will re-connect and continue acq right away.

[BrianJKoopman]

Yeah, I'd like to try to standardize how agents handle dropped connections. I wrote up some thoughts here: #538

This relates to #165, and as you point out there, just comes down to how we want to handle disconnects.