Command names containing ampersand (&) character do will not bind

[graymatter00]

Describe the bug
If a command name that contains a '&' character, such as "Do this & that", will not permanently bind to any binding category; Before Build, After Build, Clean and Project Open.

To Reproduce
In the commands.json file add commands similar to:

{
  "commands": {
    "1. Sort all CSS": {
      "fileName": "cmd.exe",
      "workingDirectory": ".",
      "arguments": "/c npm run Sort-all-CSS"
    },
    "2. ESlint": {
      "fileName": "cmd.exe",
      "workingDirectory": ".",
      "arguments": "/c npm run ESlint"
    },
    "4. GS bundle & minify CSS & JS": {
      "fileName": "cmd.exe",
      "workingDirectory": ".",
      "arguments": "/c npm run GS-bundle-minify-CSS-JS"
    },
    "5. NPM update": {
      "fileName": "cmd.exe",
      "workingDirectory": ".",
      "arguments": "/c npm update"
    },
    "6. NPM install": {
      "fileName": "cmd.exe",
      "workingDirectory": ".",
      "arguments": "/c npm install"
    }
  }
}

Note command 4 with '&' in the name.

Bind command 4 to Before Build. The command is listed in the Bindings tab, so it looks successful.

Open command.json and note that the binding entry has not been added. And no error is displayed.

Bind any of the other commands to any binding and note that the binding entry has been added to commands.json.

Change command 4's name by removing the '&' characters, bind it to any binding and note that the binding entry has been added to commands.json.

Expected behavior
I expect the binding to be added to the command.json file, or an error message should be displayed informing me that the command name cannot contain the & character, and perhaps listing all unacceptable characters.