Spurious OSC 11 command ends up writing to terminal or even executing as commands when opening vim

### Windows Terminal version

1.23.10732.0

### Windows build number

10.0.26100.3476

### Other Software

I have an issue with `11;rgb:1e1e/1e1e/1e1e;1R` sometimes appearing. It's infrequent (once or twice a day). It can happen either when I ctrl-C to cancel a running script, or when launching neovim. The former is no big deal, it just appears as text at my prompt that I can delete. But if it happens when launching vim the effect is to overwrite one character with the letter g (and leave :1e1e/1e1e/1e1e in my command history). This can be incredibly frustrating/damaging if I don't notice at the time.

I _think_ this is an issue with Windows Terminal. I've moved over from PuTTy and never experienced it there.

If it's not a bug per-se, any pointers anyone can give me to fix this would be hugely appreciated!

### Steps to reproduce

Open a file in neovim

### Expected Behavior

The file opens, unedited

### Actual Behavior

The file opens, and a single character will be replaced by a `g`. Only very occasionally, maybe one in 100 attempts.

The reported entry point is opening a file in neovim, with the same output sometimes appearing after Ctrl-C cancels a script. Start by reproducing the intermittent `11;rgb:1e1e/1e1e/1e1e;1R` output in Windows Terminal and verify that opening a file leaves it unedited and does not place the sequence in command history.

Written by the indexing model from the issue text.