Add friendly_name to dev tools "Entity" column + fuzzy search

[spacegaier]

Breaking change

Proposed change

Add friendly_name to "Entity" column in the state-dev-tools for a more user-friendly approach. Friendly name can be used for filtering as well.

This PR also adds support for fuzzy search in the entity filter.

Note: friendly_name is already shown in the "Attributes" column, but some users disable that column since too slow for big environments with many entities plus in that column the friendly_nameis not so easy to spot (although it can be filtered for i f the column is used).

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

Example configuration

Additional information

• This PR fixes or closes issue: fixes Show name in developer tools states #7581 fixes Developer Tools "states" entity column width too small #7838
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• 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

[bramkragten]

I think the entity id should stay prominent here, not the friendly name, we are in the dev tools after all.

[cdce8p]

Just my opinion, but I would prefer a fuzzy search over regex (*). I'm so used to it by now from using VS Code that I frequently notice when I'm not able to use it but expecting to.

Besides the dev -> states view, this mainly applies to dev -> services.
Also in nearly every settings view that has a filter (devices, entities, automations, scripts, ...), but that's probably out of scope for this PR.

I haven't looked in detail which fuzzy algorithm we currently use, however this is the one from VS Code: isPatternInWord.

[github-actions]

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days.
Thank you for your contributions.

[spacegaier]

I will have another look.

@cdce8p I think would be a separate PR, since that should also be then aligned with the regular entity picker. Doesn't make sense to have it in the table, but not in the general picker. Outside the scope of this PR from my side.

[bramkragten]

Maybe something like this for the layout?