Different cwd behavior in VSCodeVim and native Vim

After upgrading to vscode 1.74.2, I start observing a behavior change when openning another buffer with :e or :split in current buffer.

VSCode version: 1.74.2
VSCodeVim version: 1.24.3
Operatiing System: Windows 10

How to reproduce:

• In VSCodeVim, open up terminal with working directory as /my/path/
• Open up a buffer: code dir/foo.txt
• In buffer foo.txt, do :split <tab>, it just searchs and autocomplets files within /my/path/dir instead of /my/path.
  From this observation, it behaves like the variable autochdir is set so the cwd is changed.

Behavior in native

Things are different in native vim if I do it directly from vscode terminal.

Workaround

Currently autochdir is not supported yet thus there's no way to change this behavior on VSCodeVim.

Start by reproducing the reported :split completion behavior in VSCodeVim 1.24.3 with VSCode 1.74.2 on Windows 10, using a terminal rooted at /my/path/ and opening dir/foo.txt. Compare the resulting cwd and file completion with native Vim; done means the behavior is explained and the cwd handling matches the intended native behavior or the limitation is clearly addressed.