Don't restart gdb process when retart debug

Feature Request

When we use command "gdb a.out" to debug a program, we can use "restart" command to redebug the program, this case just restart a.out process, don't restart gdb process.

  902 ?        Ss     0:00  \_ sshd: cat [priv]
  943 ?        S      0:00  |   \_ sshd: cat@pts/5
  944 pts/5    Ss     0:00  |       \_ -bash
 1203 pts/5    S+     0:00  |           \_ gdb a.out
 2052 pts/5    t      0:00  |               \_ /home/cat/example/a.out
 
 
  902 ?        Ss     0:00  \_ sshd: cat [priv]
  943 ?        S      0:00  |   \_ sshd: cat@pts/5
  944 pts/5    Ss     0:00  |       \_ -bash
 1203 pts/5    S+     0:00  |           \_ gdb a.out                   --> not restart
 2699 pts/5    t      0:00  |               \_ /home/cat/example/a.out --> restarted

But we use vscode debugger, click the Restart command when we debuging, it will restart gdb process.

35935 ?        Sl     0:25      \_ /home/cat/.vscode-server/bin/05047486b6df5eb8d44b2ecd/node /h
19529 pts/1    Ss     0:00      |   \_ /bin/bash
43993 pts/1    S+     0:00      |   |   \_ /bin/sh /tmp/Microsoft-MIEngine-Cmd-jdpepmh2.izt
43995 pts/1    S      1:53      |   |       \_ /usr/bin/gdb --interpreter=mi --tty=/dev/pts/1
44113 ?        ts     0:00      |   |           \_ /home/cat/a.out

35935 ?        Sl     0:26      \_ /home/cat/.vscode-server/bin/05047486b6df5eb8d44b2ecd/node /h
19529 pts/1    Ss     0:00      |   \_ /bin/bash
10013 pts/1    S+     0:00      |   |   \_ /bin/sh /tmp/Microsoft-MIEngine-Cmd-rwm0evod.oem
10015 pts/1    S      1:52      |   |       \_ /usr/bin/gdb --interpreter=mi --tty=/dev/pts/1  --> restarted
10174 ?        ts     0:00      |   |           \_ /home/cat/a.out

Can we configure the vscode-debuger, make the gdb process not restart when restart debugger? bacause my a.out is very big, everytime restart gdb process will waste a lot of time.

### Tasks

Start by tracing the VS Code debugger's Restart command and its GDB process lifecycle in the TypeScript extension. Compare the behavior of a direct GDB restart with the VS Code debugger flow described here. Done means the debugger can restart the a.out process without launching a new GDB process, while preserving normal restart behavior.