Test: multiple debug consoles

[isidorn]

Refs: #31377

• any os @rebornix
• any os @dbaeumer

Complexity: 3

Have a repository which you can debug (for example our express smoke test repo), modify the launch configuration such that you can run two launch configurations at the same time (for example copying the first and just modifying the name). Start debugging and verify:

• While debugging just one session there is no difference to the old debug console, no dropdown is shown in the debug console title
• Once you start debugging the second session verify that the session dropdown appears on the top of the debug console. Verify that the dropdown is always in sync with the dropdown in the debug toolbar and that it alwasy shows the focused session / active debug console
• As you are changing the focused debug sessions, either by debugging, clicking on the stack frames or any other way the debug console always "tracks" it and shows the output for the focused debug session
• Once you have stopped debugging you can still read the content of the repl however it is readonly and there is a placeholder which explains that a debug session must be started in order to evaluate