Add support for a wider variety of EnOcean devices

[bdurrer]

Breaking Change:

Theoretically, nothing should break. The default configuration is compatible with previous versions of the component. However, since I do not own all of the devices, I cannot guarantee it. I suspect that previous commiters @rubund and @NoUsername own some of the devices. Guys, if you read this, I would be very thankful if you could spend the time to review and test this PR.

Tested with:

• 2 Rocker Switch
• Temperature Sensor

Description:

This PR adds support for temperature sensors and humidity sensors. The telegram message is now closer to the officially documented messages, which in theory should support a wider variety of devices.

As a result of the new sensors and the more generic message parsing, a refactoring was necessary. The enocean package was updated, since newer versions can do the parsing for us, moving some complexity out of the component.
The tests should make sure that the component still works for existing devices.

Note: I am away on an one week vacation, starting on the 16th. So take your time reviewing it

Related issue (if applicable): none

Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#8939

Example entry for configuration.yaml (if applicable):

sensor:
  - platform: enocean
    id: [0x20, 0x20, 0x20, 0x20]
    name: Sensor 1
    device_class: temperature
  - platform: enocean
    id: [0x20, 0x20, 0x20, 0x20]
    name: Sensor 2
    device_class: humidity
  - platform: enocean
    id: [0x20, 0x20, 0x20, 0x20]
    name: Sensor 2
    device_class: powersensor

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.

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

• Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• New dependencies have been added to the REQUIREMENTS variable (example).
• New dependencies are only imported inside functions that use them (example).
• New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
• New files were added to .coveragerc.

If the code does not interact with devices:

• Tests have been added to verify that the new code works.

[bdurrer]

I am back and the test errors (doh!) are fixed now

[MartinHjelmare]

This integration was made before we had our current standards in place. We should now adapt the integration to follow our current standards for the good of the integration.

My comments below should be read in that light.

[bdurrer]

Thanks @MartinHjelmare for the reviews. I fixed everything (I believe).

As discussed in Discord

• We keep the non-breaking
• The tests are removed and will go in a new PR
• The binary_sensor's event remains unchanged
• The binary_sensor and the enocean component in general need refactoring

[kapwebdr]

Hi, i create a pull request with a mix off your code and another pull request :
#23326
See if that's helping or not.

[MartinHjelmare]

Please don't squash commits after review has started. Sqaushing commits makes it harder for readers to track changes.

[MartinHjelmare]

Good job on the code!