fix(devices): increase socket retry limit
null ACKs from protocol 3.4 devices require us to retry to get the
actual response to a previous command.
With only one retry, eventually we strike a timing that two null ACKS
come before the response, so the connection gets treated as broken.
This will lengthen time taken to detect actual connection problems, and
to make our way through all the protocol versions in auto mode,
but seems to be necessary to get reliable communications back after several
AI submitted fixes for actual problems caused side effects for these 3.4
devices.
https://github.com/jasonacox/tinytuya/blob/master/PROTOCOL.md#troubleshooting-tips
Issue #5136