Change Insteon backend module to pyinsteon from insteonplm

[teharris1]

Breaking change

This PR will change the entity ID of some entities. Specifically the following entity types will be impacted:

• X10 dimmers, switches and sensors
• SmokeBridge sensor

Additionally, X10 entities for:

• x10_all_units_off
• x10_all_lights_on
• x10_all_lights_off

No longer appear as entities as they are not needed.

Proposed change

Change the backend module from insteonplm to pyinsteon. This change enables significant improvements to the Insteon component that include:

1. Consistent state status for changes to state outside of Home Assistant (i.e. three-way switches)
2. Improved insteon scene triggering.
3. Full coexistance with the Insteon Hub app.

All changes in the PR are specifically to enable the use of pyinsteon. The benefits above are a direct result of the use of the new module.

Type of change

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

Example entry for configuration.yaml:

# Example configuration.yaml
insteon:
  port: /dev/ttyUSB0

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request: Insteon change backend module to pyinsteon from insteonplm home-assistant.io#13296

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 homeassistant tests)
• Tests have been added to verify that the new code works.

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

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

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

• [ ]xThe manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

[MartinHjelmare]

Please be wary about the context of the functions and what api we're using, async or sync. Those need to match.

[teharris1]

@MartinHjelmare Thanks for reviewing this PR. I know it was a pain in the ars given the number of changes required.

[teharris1]

@MartinHjelmare Any chance this makes it into 0.110.x?

[MartinHjelmare]

We're passed the beta cut for 0.110.0, so no.

[MartinHjelmare]

Great!

[teharris1]

I assume there is a bigger issue with tests right now since removing that .env file should not have broken anything.