Codemirror: Switch legacy yaml to yaml

[silamon]

Proposed change

Switch the legacy yaml (codemirror 5 ported language) to yaml (codemirror 6).
Note: the highlighting seems to be different, as in the language tokens don't match, not sure if that's important.

Edit: I've setup a demo page to test for anyone that wants to: https://deploy-preview-20844--home-assistant-gallery.netlify.app/#misc/codemirror

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 Escaping of ' is missing in the Developer tools, leading to wrong syntax highlighting #11576 fixes Codemirror: Switch legacy yaml to yaml (design test) #20844
• This PR is related to issue or discussion:
• 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

[steverep]

Note: the highlighting seems to be different, as in the language tokens don't match, not sure if that's important.

Does the theme need to be tweaked?

[silamon]

Note: the highlighting seems to be different, as in the language tokens don't match, not sure if that's important.

Does the theme need to be tweaked?

I've setup a demo page to test for anyone that wants to: https://deploy-preview-20844--home-assistant-gallery.netlify.app/#misc/codemirror
Unfortunately, I don't use yaml too much to see most of the changes.

One of the most visible changes in the given example below is the key being colored differently (yellow vs brownish red):

# Basic syntax - key and value separated by colon and space before the value
key: value

[bramkragten]

It doesnt make a difference anymore based on the type of the value (string, number, boolean)

The other differences in color could be fixed in the theme.

[silamon]

It doesn't seem like the tokenizer of the new incremental grammar supports that. The token should be defined as a boolean or a number, and we define a style for that, but it isn't tagged as a boolean or a number token at first.