Reorganize insteon code

[teharris1]

Breaking change

The Insteon entity device state attributes were changed to conform to naming standards. Insteon Address is now insteon_address and Insteon Group is now insteon_group. Users may need to update automations and scripts that rely on these attributes.

Proposed change

Reorganize the insteon component code to make future edits easier.

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:

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:

• The 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]

Good!

Can be merged when the breaking change paragraph is updated. Please ping me when that is done.

[teharris1]

@MartinHjelmare I have added the paragraph to the breaking change section but I am not sure there is anything a user needs to do to cope with that change since I don't believe the attributes are used for anything other than documentation.

[MartinHjelmare]

Ok. I added a sentence about automations and scripts where it at least theoretically could be used.

[MartinHjelmare]

Let's wait with merging this until the beta for 0.105 is cut later today. Then there's more time for further PRs with breaking changes for this integration this release cycle.