Add entity_category and is_entity_category to templates

[Petro31]

Breaking change

Proposed change

Filling a feature request for the ability to get the entity_category for a given entity_id.

https://community.home-assistant.io/t/add-the-entity-category-to-the-available-state-object-properties/378724

Listing the category

{{ label_entities('my_label') | map('entity_category') | list }} 

Checking the category(ies)

{{ label_entities('my_label') | select('is_entity_category', 'config') | list }}
{{ label_entities('my_label') | select('is_entity_category', ['config', 'diagnostic']) | list }} 

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.

To help with the load of incoming pull requests:

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

[CloCkWeRX]

Seems sensible, 26 people find it useful

[frenck]

Looks good! However, documentation is missing.

Additionally, I want to do a quick check with the core team if this is functionality we want to expose. I have added it to the architectural meeting agenda, and will get back on that this week.

../Frenck

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[Petro31]

Looks good! However, documentation is missing.

Additionally, I want to do a quick check with the core team if this is functionality we want to expose. I have added it to the architectural meeting agenda, and will get back on that this week.

../Frenck

Was waiting on approval before writing the documentation. Been bit by that a few times, not looking forward to wasting my own time with doc changes for something that gets rejected.