Avoid creating binary sensor for unsupported attributes

[elupus]

Some of these are virtual attributes updated but "toggle" events the the OnOffClusterHandler, but not really supported by the device itself.

[elupus]

No idea why this is here, it was in one of the other handler like this.

[codecov]

Codecov Report

Attention: Patch coverage is 77.77778% with 2 lines in your changes missing coverage. Please review.

Project coverage is 95.67%. Comparing base (3a1e0d6) to head (41bfc3a).
Report is 22 commits behind head on dev.

Files	Patch %	Lines
...ha/application/platforms/binary_sensor/__init__.py	77.77%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##              dev     #144      +/-   ##
==========================================
+ Coverage   95.64%   95.67%   +0.02%     
==========================================
  Files          61       61              
  Lines        9232     9264      +32     
==========================================
+ Hits         8830     8863      +33     
+ Misses        402      401       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[elupus]

Okey,. this is not going to fly. The whole stuff with handle_on_off_output_cluster_exception makes things weird here. We hook up the server cluster handler to the client (out) cluster.
How much will break if we drop that?

As far as i understand there are some weird Tuya devices that make use of this strangeness as well as perhaps some LUMI stuff (

zha/tests/zha_devices_list.py

Line 3088 in 9fe8345

1: {

)

[elupus]

I've opened #145 to try to figure out a better solution.