Incorrect cursor position when type hints are present

Describe the bug
When on the first character of a function argument for which the language extension provides a type hint, the cursor positions itself on the type hint rather than the actual first character. See screen capture below with a Javascript example.

To Reproduce

1. click on the second character of an argument name
2. Hit 'h' to move the cursor by one character left
3. Voilà...

Expected behavior
The cursor should position itself on the first character of the argument name, not on the type hint (herebelow on the "m" of "msg", not on the "e" of the "error:" type hint)

Screenshots

Environment (please complete the following information):

• Extension (VsCodeVim) version: v1.21.10
• VSCode version: 1.63.2
• OS: Windows 10

Additional context
ESLint extension from Microsoft v2.2.2, which provides the type hints.

Reproduce the issue in VSCode 1.63.2 with VSCodeVim v1.21.10 and the ESLint extension v2.2.2, following the three steps in the report. Trace the cursor movement behavior when type hints are visible; done means moving left from the second argument character places the cursor on the argument's first character rather than the hint.