Allow inheriting base component entity descriptions in frozen dataclasses

[emontnemery]

Proposed change

Allow inheriting base component entity descriptions in both frozen and mutable dataclasses

This is a follow-up to #105211

Background in PR #105211

Depends on:

• Improve FrozenOrThawed #105541
• Fix entity descriptions in philips_js #105625
• Avoid mutating entity descriptions in efergy #105626
• Avoid mutating entity descriptions in efergy tests #105717

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)
• 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.

[bdraco]

LGTM if CI passes

[bdraco]

Looks like there is one integration left to fix
FAILED tests/components/efergy/test_sensor.py::test_sensor_readings - dataclasses.FrozenInstanceError: cannot assign to field 'entity_registry_enabled_default'
FAILED tests/components/efergy/test_sensor.py::test_multi_sensor_readings - dataclasses.FrozenInstanceError: cannot assign to field 'entity_registry_enabled_default'

[emontnemery]

Looks like there is one integration left to fix FAILED tests/components/efergy/test_sensor.py::test_sensor_readings - dataclasses.FrozenInstanceError: cannot assign to field 'entity_registry_enabled_default' FAILED tests/components/efergy/test_sensor.py::test_multi_sensor_readings - dataclasses.FrozenInstanceError: cannot assign to field 'entity_registry_enabled_default'

Weird, that was supposed to be fixed by #105626

Oh, the efergy tests also mutate the entity descriptions 🤦

[bdraco]

Let's hope the CI passes now