Use Hyperion human-readable effect names instead of API identifiers

[dermotduffy]

Proposed change

Hyperion itself uses one set of identifiers in its API to refer to components/"sources" (e.g. "GRABBER", "V4L"), but its UI uses a different set of friendlier names (e.g. "Platform Capture", "USB Capture"). The home assistant integration currently uses the "unfriendly" API identifier in the light component, but the friendly UI names in the switch component.

This change deprecates these API identifiers (they won't be shown in the list, but automations that use them will still work and will print a warning).

Once this change is submitted, the switch component, light component and the Hyperion UI will all be using the same names.

Underlying library changes: dermotduffy/hyperion-py@v0.7.0...v0.7.2

Home Assistant Hyperion component:

Hyperion-UI (remote panel):

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:

None.

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue: Turning off Hyperion light via Home Assistant turns off Hyperion for other sources #41892
• Link to documentation pull request: Don't refer to deprecated Hyperion effect names home-assistant.io#16363

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

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[github-actions]

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days.
Thank you for your contributions.

[dermotduffy]

This PR is still live, still desired and I'm still happy to respond to any feedback if someone has time to review. Thank you.

[dermotduffy]

[April update, rebased from dev] This PR is still live, still desired and I'm still happy to respond to any feedback if someone has time to review. Thank you.

[frenck]

Thanks, @dermotduffy 👍

../Frenck 🚂

[dermotduffy]

Thank you!