Fix flaky diagnostics test for Novy Cooker Hood

[balloob]

Proposed change

The Novy Cooker Hood diagnostics output includes the list of entities returned by er.async_get(...).entities.get_entries_for_config_entry_id(...). The registry does not guarantee a stable ordering across runs, which leads to occasional snapshot mismatches in tests/components/novy_cooker_hood/test_diagnostics.py::test_diagnostics — the fan and light entities show up in different orders.

Noticed on CI as a flaky failure:

FAILED tests/components/novy_cooker_hood/test_diagnostics.py::test_diagnostics - AssertionError: assert [+ received] == [- snapshot]
    dict({
     ...
      'entities': list([
  -     dict({
  -       ...
  -       'entity_id': 'fan.novy_cooker_hood',
  -       ...
  -     }),
        dict({
        ...
        }),
  +     dict({
  +       ...
  +       'entity_id': 'fan.novy_cooker_hood',
  +       ...
  +     }),
      ]),
     ...
    })

Sort the entities by entity_id before serializing them in the diagnostics payload so the output is deterministic.

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:
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• 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.
• 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

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 diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

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

---

Generated by Claude Code

[home-assistant]

Hey there @piitaya, mind taking a look at this pull request as it has been labeled with an integration (novy_cooker_hood) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of novy_cooker_hood can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant mark-draft Mark the pull request as draft.
• @home-assistant ready-for-review Remove the draft status from the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign novy_cooker_hood Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant update-branch Update the pull request branch with the base branch.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the pull request.

[Copilot]

Pull request overview

This pull request makes Novy Cooker Hood diagnostics deterministic by sorting entity registry entries before serializing them, eliminating a flaky snapshot test caused by non-stable entity registry ordering.

Changes:

• Sort the entity registry entries by entity_id before building the "entities" list in the diagnostics payload.