Block cursor remains in files, even after vim toggled off

Describe the bug
When you toggle vim on, your cursor goes from being a caret to being a block cursor. When you toggle vim off, it goes back to being a caret.

However, when you toggle vim off, and then switch focus into other open tabs, the open tabs still have the block cursor.

To Reproduce

1. Open 2 code tabs with Vim extension enabled. Note block cursors.
2. Focus one code tab and toggle vim off with the toggleVim command. Note the cursor switched from block cursor to caret.
3. Switch to the other code tab. Notice that tab still has a block cursor.

Expected behavior
When you use toggleVim to enable/disable vim, it should change the caret across all open tabs. Not just the currently selected one.

This is, visually, the most apparent mechanism for determining what state your current tab is in. I often toggle between vim mode and standard mode.

Screenshots

Here you can see me toggling VS code off in one tab but the block cursor remains in the other tab.

https://github.com/VSCodeVim/Vim/assets/6633831/26113e1a-4304-4e53-a74c-3a5340aa470a

Environment:

• Extension (VsCodeVim) version: 1.26.0
• VSCode version: 1.82.2
• OS: Windows 11

Start by reproducing the issue with two open code tabs, then trace the toggleVim command and the cursor state handling in the extension. The fix is complete when toggling Vim updates the cursor in every open code tab, and the relevant tests pass or are added for this two-tab scenario.