Add scoring and sorting to sequence matcher

[donkawechico]

Proposed change

Add scoring to the filter algorithm to make more relevant filters appear first in the list.

The current simple sequence matching algorithm doesn't score matches, so if a low-quality result is higher alphabetically, it will appear first, resulting in a confusing experience.

For example, "media" will match "automation.choose_duplicate" before it matches "media_player.bedroom" simply because "automation" starts with an "a".

This PR ports over VS Code's implementation of filter for its quick access bar.

The filter code is lazy-loaded after user launches quick bar.

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 #
• 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

[zsarnett]

Since we stole this from VSCode. Lets make a comment at the top of each "stolen" file or function that is copied.

[zsarnett]

I meant to comment not approve...

[zsarnett]

Also, this is going to be difficult to review. Just as a quick glance. Do we need ALL of the checks?are we comparing case? like if case the same then if it isn't the same and comparing both. We should probably only do one or the other. But again only glanced. Vscodes implementation may be more powerful than we need.

[donkawechico]

Do we need ALL of the checks?are we comparing case?

We definitely don't need all of the checks. But we don't need all the features of fuse.js, but we import them all anyway. This is sort of just a library import.

I realize that's not a water-tight argument. I'm just not sure I see the value in spending a long time deciphering the code, surgically removing the features we aren't currently using, only to later discover they'd be quite helpful.

All that being said, now that I know we can get what we want using only fuzzyScore and matchesSubString, I could at least go through and remove anything unrelated to those two functions.

[donkawechico]

Since we stole this from VSCode. Lets make a comment at the top of each "stolen" file or function that is copied.

Confession time. HA is my first meaningful contribution to open source anything. I don't know the proper way to apply credit, so I just replaced the existing microsoft copyright declaration at the top of each borrowed file with the contents of VS Code's license.txt.

I didn't put any MS credit in sequence-matching.ts because that's all my code.

Is that correct?

Mistake