VSCodeVim does not allow single definitions of keybindings for multiple keybinding types

The Issue

We have normalModeKeyBindingsNonRecursive for normal mode keybindings, visualModeKeyBindingsNonRecursive for visual mode keybindings. But there's no way to define a keybinding that applies to 'both normal and visual modes'. Instead, it has to be duplicated in each of the keybinding arrays.

An Example

I want <leader>p to pin the current file, and I want it to work in normal and visual modes. In my .vimrc I'd have something like:

noremap <leader>p pin_function

But for VSCodeVim I need:

"vim.normalModeKeyBindingsNonRecursive": [
  { 
    "before": [ "<leader>", "p" ], 
    "commands": [ "workbench.action.pinEditor" ] 
  },
],
"vim.visualModeKeyBindingsNonRecursive": [
  { 
    "before": [ "<leader>", "p" ],
    "commands": [ "workbench.action.pinEditor" ] 
  },
],

Solution Idea

Introduce a new keybinding interface in config, vim.keybindings, to which you supply:

a) A boolean that defines whether the keybinding is recursive,
b) An array of characters that specify the modes the keybinding should apply to (e.g. n, v)
c) The keybinding

For example:

"vim.keybindings": [
  { 
    "recursive": true,
    "modes": ["n", "v"], 
    "before": [ "<leader>", "p" ], 
    "commands": [ "workbench.action.unpinEditor" ] 
}]

Another idea would be to supply the mapping definition to the keybinding (e.g. "definition": "noremap") and have the VSCodeVim extension work out whether it's recursive and what modes it should apply to.

Start by locating the existing normalModeKeyBindingsNonRecursive and visualModeKeyBindingsNonRecursive configuration handling and comparing their recursive and mode-specific behavior. Define how a shared vim.keybindings configuration should represent modes and recursion, then verify that one binding can apply to both normal and visual modes without requiring duplication while preserving existing configuration.