[Bug] YAML keyword values affected by comments

Reproducible in vscode.dev or in VS Code Desktop?

• Not reproducible in vscode.dev or VS Code Desktop

Reproducible in the monaco editor playground?

• Not reproducible in the monaco editor playground

Monaco Editor Playground Code

monaco.editor.create(document.getElementById('container'), {
	value: "keyword-control: null\nstring-control: string\n\nexample1: null #Highlights as string but evaluates null\nexample2: null#Highlights as keyword but evaluates as string\n",
	language: 'yaml'
});

Actual Behavior

Keywords (null, true, false, etc) are incorrectly highlighted as strings if a there is a comment on the same line as the keyword (example1). If the comment is touching the keyword, the highlighting is correct but the value is interpreted as a string when parsed (example2).

Expected Behavior

I would expect that in both examples, the null would highlight as a keyword and that the value would be evaluated as null, not a string.

Additional Context

No response