adafruit_wiznet5k_socket.py has hardcoded 1000 second timeouts

[e28eta]

Related, but separate, to #89

There are at least two hardcoded timeouts for 1000:

Adafruit_CircuitPython_Wiznet5k/adafruit_wiznet5k/adafruit_wiznet5k_socket.py

Lines 178 to 189 in 73bb5b6

	def __exit__(self, exc_type, exc_val, exc_tb) -> None:
	if self._sock_type == SOCK_STREAM:
	self.disconnect()
	stamp = time.monotonic()
	while self.status == wiznet5k.adafruit_wiznet5k.SNSR_SOCK_FIN_WAIT:
	if time.monotonic() - stamp > 1000:
	raise RuntimeError("Failed to disconnect socket")
	self.close()
	stamp = time.monotonic()
	while self.status != wiznet5k.adafruit_wiznet5k.SNSR_SOCK_CLOSED:
	if time.monotonic() - stamp > 1000:
	raise RuntimeError("Failed to close socket")

I believe time.monotonic() returns the number of seconds. Waiting 1,000 seconds (over 16 minutes) in the __exit__ block is far too long.

[tekktrik]

Yeah, that does seem extremely long. @dhalbert, I know we're exploring (or actively) changing the socket libraries. Do you think it's worth waiting to change this with that work, or go ahead and add a fix/improvement in the meantime?

[FoamyGuy]

fwiw I think we should accept a fix in the meantime if one gets submitted.

My assumption is that this was intended to be 1000ms or 1 second but the units got mixed up. I intend to test it out with lower values this week. Will submit a PR if testing is successful and no one else has submitted yet.

[BiffoBear]

The default hardware timeout settings mean that the hardware will timeout after 19 seconds. This will make a good stopgap. Eventually, polling the hardware timeout register will be a better alternative because it will respect any changes to the hardware timeout settings made by the user.

I'll open a PR with 19 seconds.