Move Alexa entity id generation into abstract config class

[mback2k]

Proposed change

This makes it possible to change the ID schema in implementations.

I am currently working on an Alexa integration using the Alexa Voice Service (AVS) SDK which makes exposing Home Assistant to the internet and running a skill on AWS Lambda obsolete. Instead Home Assistant will directly connect to AVS servers and provide a backchannel for connected Smart Home endpoints. I already have a fully functioning prototype running locally, but need this change in core as a basis for the new integration based upon the AbstractConfig class.

Detail background for this change: AVS needs connected Smart Home endpoints (e.g. Home Assistant Devices/Entities) to follow a specific ID schema, like this: {client-id}::{product-id}::{device-serial-number}-{entity-id}.

This doesn't break existing behavior, code or integrations. It just makes it possible to overwrite this function. Therefore, I am looking forward to get this merged, thank you!

Type of change

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

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
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format 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.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

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

[home-assistant]

Hey there @home-assistant/cloud, @ochlocracy, @jbouwh, mind taking a look at this pull request as it has been labeled with an integration (alexa) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of alexa can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign alexa Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[jbouwh]

LGTM,
Thnx @mback2k 👍