"Disabling vim" doesn't actually disable vim when using the go to file shortcut to enter a file.

[ArcaneWizard]

Describe the bug
To quickly switch files in Visual Studios, I often use the Edit.GoToFile Shortcut. If I set VsVim to disabled, then use the Edit.GoToFile shortcut to go to a different file in the SAME project, the VsVim flashing cursor reappears in the newly opened file. However, VsVim is still labeled as "Disabled" in settings.

To Reproduce

1. Create a project with multiple files.
2. Open the options panel (Tools > Options), and under Environment > Keyboard, set a shortcut for Edit.GoToFile. Alternatively, use the default Edit.GoToFile shortcut (possibly Ctrl + Shift + T)
3. Under Environment > Keyboard, look up the word "vim" and add a shortcut for VsVim.ToggleEnabled.
4. In a file, use the toggle VsVim shortcut. At the bottom of Visual Studios, it should say "Vim Disabled".
5. Use the Edit.GoToFile shortcut to teleport to a different file in the project.
6. Note that the vim flashing cursor suddenly reappears. Vim shortcuts work too.
7. Open the options panel, and in VsVim, scroll down to the Disable VsVim property. Confirm that it is still set to true.

Expected behavior
If I go to a different file with the Edit.GoToFile shortcut, and I have VsVim disabled, I expect the vim flashing cursor to not suddenly reappear (especially since Visual Studios claims VsVim is still disabled).

Screenshots
NA

Environment (please complete the following information):

• Visual Studio version: 2022 community
• VsVim version: 2.10.0.6
• Programming Language: c#
• Check(Type 'x') any that are installed:
  • ReSharper
  • Visual Assist

Additional context
Specifically, I'm using a Unity codebase / C# sln.

Note:
The following is written about contributing.
https://github.com/VsVim/VsVim/blob/master/CONTRIBUTING.md

General Keyboard configuration problems are described below.
#2527