feat: implement colour contributions for debug REPL

[Robert Rossmann (robertrossmann)]

This PR fixes #97695.

Most of the debug REPL components are now theme-able. 🎉 🎨 The following new colour contributions have been added:

• debugConsole.infoForeground: info-level messages
• debugConsole.warningForeground: warning-level messages
• debugConsole.errorForeground: error-level messages
• debugConsole.sourceForeground: foreground colour of the source filename which generated the log message
• debugConsoleInputIcon.foreground: icon colour which marks the evaluation input. I remember seeing a very specific name for this icon but I cannot remember. I will happily update the naming of this contribution to match if this is not accurate.

Chores

I have moved the theming support for REPL out of the repl.ts file so we have it in one place.

[Isidor Nikolic (isidorn)]

Robert Rossmann (@robertrossmann) great PR as usual! Thanks a lot 👏

1. I am convinced that we need all those colors except debugRepl.expressionForeground. We already have debugTokenExpression.name and debugTokenExpression.value. And I belive that the repl should just use those colors for coloring expressions. Why should the debugRepl have different colors and not be consistent with the other debug views?
2. We never call it debugRepl to whatever is user facing, thus I suggest that the names of the colors are debugConsole.

Adding Martin Aeschlimann (@aeschli) as a reviewer for color names
fyi Benjamin Pasero (@bpasero)

[Benjamin Pasero (bpasero)]

Thanks for pushing this. Would be great to eventually have all of debug be fully themable 👍

[Robert Rossmann (robertrossmann)]

Isidor Nikolic (@isidorn) Thanks for the suggestions!

I will drop debugRepl.expressionForeground. To be honest, I don't like it that much, either. Instead, I will use the debugTokenExpression.value as the colour for the evaluated expression in the console. Though I am unsure where I would use the debugTokenExpression.name. 🤔

I'll rename the colour scope to debugConsole. Makes sense. 👍

[Robert Rossmann (robertrossmann)]

Isidor Nikolic (@isidorn) updated now, with some deviations noted below. ℹ️

• I noticed that on high-contrast theme, the debugConsole.inputMarkerIconForeground was poorly visible so I cranked up the opacity back to 1 to make it stand out.
• I tried to use the debugTokenExpression.value colour for the evaluated expressions in the REPL, but it looked... dull. The built-in themes use a dimmed-down variant of the foreground text colour for this and it made it look like a comment, or a footnote, or generally something unimportant. I ultimately decided to not allow theming this part of the UI. Another reason for this decision was that I noticed that as I type the expression into the input box, I get pretty good syntax colouring. 🎨 This colouring is currently discarded when the expression is shown in the console after I press Enter and I think it would be awesome to have this highlighting carry over to the console, making this particular colour contribution redundant. 💯

Let me know what you think. ❤️

[Isidor Nikolic (isidorn)]

Thanks a lot. Your changes look great thus approving.
As for the coloring of evaluated expressoins in the REPL, I agree with you and I think we can tackle that in a sepearte Feature Request / PR.

Though let's wait just for Martin Aeschlimann (@aeschli) to approve the color names and then we can merge this.

[Isidor Nikolic (isidorn)]

Robert Rossmann (@robertrossmann) after discussing with Martin Aeschlimann (@aeschli) we like all the color names except debugConsole.inputMarkerIconForeground
Can you please change it to debugConsoleInputIcon.foreground

[Robert Rossmann (robertrossmann)]

Isidor Nikolic (@isidorn) Updated! ✅

[Isidor Nikolic (isidorn)]

Looks great. Thanks for doing this. Merging in 🎉