Support separate VSCodium plugins folder

[laert-ll]

Feature idea

VSCodium does not support all the plugins that VSCode does.

While installing VSCodium, instead of installing the plugins for VSCode ($IDE_HOME/settings/vscode/plugins), we should create a dedicated $IDE_HOME/settings/vscodium/plugins directory which contains only the plugins officially supported by VSCodium. The system should check here first and fall back to $IDE_HOME/settings/vscode/plugins if not present.

See: #1888.

Additional context

No response

[hohwille]

From the title of the issue I expected that we would support for $IDE_HOME/settings/vscodium/plugins if present and fall back to $IDE_HOME/settings/vscode/plugins if not present.

From the issue description I get the impression that we want to maintain a (hardcoded?) list of plugins that are incompatible to VSCodium.

@laert-ll can you refine the issue so it gets clear what should be implemented here? We can also do that together with the team in daily or KT session. Unless this is done, we should not set ready-to-implement label.