Support proxy of binary messages from addons to HA

[mdegat01]

Proposed change

Currently supervisor can only proxy messages of type text from addons to HA. Some addons need to be able to send binary messages as well.

Type of change

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

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:
• Link to cli pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast supervisor tests)
• Tests have been added to verify that the new code works.

If API endpoints of add-on configuration are added/changed:

• Documentation added/updated for developers.home-assistant.io

[pvizeli]

lgtm. Maybe not hard break if the type is not supported, only log it for not break on unknown things

[mdegat01]

@pvizeli I was just trying to keep behavior as it was today:

supervisor/supervisor/api/proxy.py

Line 233 in a70f81a

await client.send_str(server_read.result())

If send_str is passed anything other then a string today it will raise TypeError just like I am. If we think that's aggressive I can change it. Although the problem with only logging it is whoever sent the message will have no idea something went wrong. The user will see the log but they can't do anything about that since this is communication between addon and HA.

EDIT: Also I should note, it will actually just log it and close the connection on TypeError:

supervisor/supervisor/api/proxy.py

Lines 245 to 246 in a70f81a

	except (RuntimeError, ConnectionError, TypeError) as err:
	_LOGGER.info("Home Assistant WebSocket API error: %s", err)