These are kind of "citizen developers", using the folder structure using one namespace at a time. Each feature which they work on has its own namespace, which might be deleted when the feature is approved and merged into the main branch. They can understand that a namespace has been deleted, but not being able to select another one by using the normal VSCode UI will be a bad experience for them as this might happen quite regularly.

FYI

The codeQuality tool now requires a newer java version. I had to change this in the settings.json from

"sonarlint.ls.javaHome": "/Library/Java/JavaVirtualMachines/temurin-11.jdk/Contents/Home"

to 

"sonarlint.ls.javaHome": "/Library/Java/JavaVirtualMachines/temurin-21.jre/Contents/Home"

I skipped version 17 as there was already a 21 which seems to work OK.

I used the OpenJDK runtime:

https://adoptium.net/temurin/releases/

Thanks @Robert Cemper

Since my specific case is for the EU, I think the simplest solution is to use $ZTZ to correct for basic time zone. The rules for summertime are always the same in this area (until they change it, the discussion flares up two times a year). I already found some pseudo-code for that. If summertime, subtract another 60 minutes from $ZTZ. Not as generic as I wanted, but good enough for my case.