Remove domain prefix from actions

[bramkragten]

Proposed change

Since work has been done to change the name of actions to align with the name of triggers and conditions, it is not longer needed to prefix the name of actions with the domain name.

TODO: check if everything is migrated, what to do with (custom) integrations providing actions that might now miss the prefix.

Screenshots

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• 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 or discussion:
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to backend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• The code change is tested and works locally.
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

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

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

To help with the load of incoming pull requests:

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

[piitaya]

For custom integration, we can still prefix them right? But not sure how to detect that

[bramkragten]

Yeah, we have things like Sonos:

Or recorder:

Etc...

[bramkragten]

Maybe just remove the prefix from entity type integrations for now...?

[piitaya]

Yeah it can be a solution !