Extraneous downward movement with `gj`, `gk`, `g$`

Describe the bug

Visual line movement (i.e. gj, gk, g$ etc.) behaviors are broken when the cursor is placed at the end of a wrapped line that happens to be longer than the line above or below it. There will be an extraneous downward movement of 1 line, putting the cursor 1 line below its expected position.

To Reproduce

Set editor.wordWrap to bounded. Type the text below (as a single line) in VSCode. Reduce the width of the VSCode window until the visually displayed text is wrapped identically to what's shown below.

This is a piece of example text 
that is soft-wrapped to multiple 
visual lines, to demonstrate an 
issue with the plugin.

Place the cursor at the very end of the 2nd line (i.e. the space character after "multiple").

1. Pressing gj moves the cursor to the beginning of the 4th line.
   Expected behavior: cursor moves to end of 3rd line.
2. Pressing gk will move the cursor to the beginning of the 2nd line.
   Expected behavior: cursor moves to end of 1st line.

As for the behavior of g$:

Place the cursor at the very beginning of the 2nd line. Pressing g$ brings the cursor to the beginning of the 3rd line. Expected behavior: cursor to be moved to the end of the 2nd line. This issue was raised in #2032 back in 2017 but seems like it hasn't been addressed.

Environment:

• Extension (VsCodeVim) version: v1.25.2
• VSCode version: 1.80.1
• OS: macOS Monterey 12.4 (21F79)

Reproduce the movement in VSCode with editor.wordWrap set to bounded, using the text and cursor positions from the issue. Trace the visual-line movement handling for gj, gk, and g$, then verify that each movement lands on the expected visual line and that the behavior is covered by regression checks.