Convert isy994_control Events to Device Events and Device Triggers

[shbatm]

Update the Home Assistant integration to use Device Events and Device Triggers instead of just the isy994_control event structures. This will allow selection in the UI for automations.

[shbatm]

This was migrated from shbatm/hacs-isy994#59.

Original Issue Text:

As originally flagged here: home-assistant/core#35225 (comment)

Opening an issue here to allow discussion and development/testing of a migration plan for isy994_control events to fit the updated Home Assistant design guidelines.

Some initial thoughts:

• The control events from the PyISY pick up all the state attribute changes (anything that isn't a ST command). If you don't listen to them, things like thermostats, zwave multisensors, and NodeServer nodes won't ever change state in HA.
• Control events firing in HA allow automations to pick up on differences in commands (DFON vs DON) and to find out what the controlling device was (e.g. Reacting to a switch being pressed vs a light state change which could have been done by anything). This seems on the surface like it fits with the newer device triggers, but I'm not that familiar with them yet.
• Currently, we have to include entities for 'uncontrollable devices' like the remotelincs, just to get the events. It'd be nice if we could get these events without the need for a separate (otherwise useless) entity.