Support editor::SpawnNearestTask with runnables hidden

[baldwindavid]

#19901 added the editor::SpawnNearestTask command that will run the task tied to the nearest "runnable". This is handy to, for example, run the test nearest the current cursor position.

Runnables are displayed in the gutter if the gutter.runnables setting is true. If this setting is false the runnables are hidden from the gutter.

I have always run tests under cursor, but have been mostly working in one language so hard-coded a keybinding to spawn a task in that specific language. I'd now like to generalize this a bit. The simplest way I think would be to run this nearest task command. However, the command only seems to work if that gutter.runnables setting is true. I use vim mode and would never run a test via clicking a button. This runnable play button just clutters the interface for me so I hide it.

I'd like to be able to run this command even if runnables are hidden from the gutter. I can understand why it was originally setup tied to this gutter setting, but there's all kinds of things that you interact with even though you can't see them; basically everything in vim 😄. I think this is similar, but perhaps there is an additional technical component that drove this behavior.