Add receive_timeout to RyobiWebSocket ws_connect to fix issues with dropped connections

[CJOWood]

Proposed change

Fixes an issue where the aiohttp library websocket connection seems to silently drop out, only throwing an exception once a command has been attempted. receive_timeout should ensure we get a response from Ryobi's server within the currently set 5 minutes. This may not be an ideal value and is an estimate based on another library's fix for the same/similar issue (they have implemented aiohttp slightly differently).

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (which adds functionality to an this integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

This PR is likely related to (external library) issue:

• WebSocketResponse does not throw/close when connection is abruptly cut aio-libs/aiohttp#2309
• WebSocketResponse requires closing/closed checks before sending something aio-libs/aiohttp#3391

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• The code has been formatted using Black (black --fast custom_components)

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated to README.md