[JavaScript] Tokenization breaks when new line starts with less-than operator

首先，在禁用扩展的 VS Code 中重现 JavaScript 示例，然后检查仓库的 TypeScript 语法文件。当行首的 less-than 运算符被高亮为运算符而不是开启 JSX，并且高亮不会持续到闭合标签时，修复就完成了。

Does this issue occur when all extensions are disabled?: Yes

VS Code version: Code 1.66.0 (e18005f0f1b33c29e81d732535d8c0e47cafb0b5, 2022-03-30T05:50:41.156Z)
OS version: Linux x64 4.15.0-175-generic
Restricted Mode: No

Simple example

1. In a new editor, set the language mode to plain JavaScript
2. Type the following

   let obj = {}
   
   let bad = 1
     < obj.two
   
   let unexpected = 1
   />
   let nowFixed = 1
   

3. The < on line 4 is treated as a JSX tag opener (even when the self-closing tag on line 7 is removed)
   Note how GitHub's highlighting in 2. and this screenshot disagree
   
4. Declaring two slightly changes highlighting, but notice the . in obj.two is still green. Using "Developer: Inspect Editor Token and Scopes" shows it's still considered a JSX tag.
   

Extended example

To show all the specific conditions required to trigger this issue

let expected, notExpected, obj = {}
let expectedFunc = () => { return (true) }
obj.twenty = 20

expected = 10 < obj.twenty

expected = 10
  < 20

expected = 30
  > obj.twenty

expected = 10
  < obj.twenty;

expected = (10
  < obj.twenty)

expected = 10 <
  obj.twenty

notExpected = 10
  < obj.twenty // <-- `<` at start of line misinterpreted as JSX

// syntax highlighting continues to be wonky
let notExpectedFunc = () => { return (true) }
/> // until a JSX closing tag is added
let expectedFunc = () => { return (true) }

Real-world example

In my repo, using prettier for formatting (specifically, a prettier fork that places operators at start of line instead of end) yields the following output, with the problem starting at line 77. Note how placing the cursor on the less-than op highlights the greater-than op on line 84, as if lines 77-84 are just one giant JSX opening tag declaration. Also note that this is a .js file with no mention nor import of React, and the prior examples also had language type explicitly set to JavaScript.

My preemptive apologies if this issue is a duplicate (I searched but found none) or if it belongs in a more specific repo.