Error: Unsupporten token type: error at l

Describe the bug

Reported by telemetry on 1.4.0 version.

Stack trace:

Error: Unsupporten token type: error 
at l (c:\Users\_username_\.vscode\extensions\redhat.vscode-yaml-1.4.0\dist\languageserver.js:2:612577) 
at Object.t.resolveFlowCollection (c:\Users\_username_\.vscode\extensions\redhat.vscode-yaml-1.4.0\dist\languageserver.js:2:626550) 
at Object.t.composeCollection (c:\Users\_username_\.vscode\extensions\redhat.vscode-yaml-1.4.0\dist\languageserver.js:2:610252) 
at Object.l [as composeNode] (c:\Users\_username_\.vscode\extensions\redhat.vscode-yaml-1.4.0\dist\languageserver.js:2:612477) 
at Object.t.composeDoc (c:\Users\_username_\.vscode\extensions\redhat.vscode-yaml-1.4.0\dist\languageserver.js:2:611502) 
at t.Composer.next (c:\Users\_username_\.vscode\extensions\redhat.vscode-yaml-1.4.0\dist\languageserver.js:2:616774) 
at next (<anonymous>) 
at t.Composer.compose (c:\Users\_username_\.vscode\extensions\redhat.vscode-yaml-1.4.0\dist\languageserver.js:2:616473) at compose.next (<anonymous>) at Function.from (<anonymous>)

Look like it bug in yaml parser

Start by tracing the reported failure in dist/languageserver.js, especially the flow-collection and composeNode calls in the stack trace. Find a YAML input that produces the unsupported error token, then verify that parsing no longer throws for that input and add a regression test if the relevant test location can be identified.