[Bug] Terminal setup checks wrong VSCode config path for Insiders edition

Bug Description

/terminal-setup

⎿ Found existing VSCode terminal Shift+Enter key binding. Remove it to continue.
See /Users/__/Library/Application Support/Code/User/keybindings.json

/terminal-setup

⎿ Found existing VSCode terminal Shift+Enter key binding. Remove it to continue.
See /Users/__/Library/Application Support/Code/User/keybindings.json

I'm using vscode insiders so I think the logic is wrong for this check. I've removed said bindings in

insiders already but the logic seems to check normal vscode keybindings -_-

⏺ Update(~/Library/Application Support/Code/User/keybindings.json)
⎿ Removed 8 lines
107 {
108 "key": "alt+cmd+n",
109 "command": "workbench.panel.chat.view.copilot.focus"
110 -},
111 -{
112 - "key": "shift+en
113 - "command": "workbench.action.terminal.sendSequence",
114 - "args": {
115 - "text": "\^[\r"
116 - },
117 - "when": "terminalFocus"
110 }
111 ]
112 No newline at end of file

⏺ Done! Removed the Shift+Enter binding.

Environment Info

• Platform: darwin
• Terminal: vscode
• Version: 2.0.74
• Feedback ID: faeea213-e692-45e6-a63f-a50f99e5d345

--- Edit

/terminal-setup

⎿ Installed VSCode terminal Shift+Enter key binding
See /Users/__/Library/Application Support/Code/User/keybindings.json

It then only installs the normal vscode keybindings so doesn't actually work.

Errors

[]