Something fishy is going on with Sonar Cloud again

SonarQube Cloud
4

Put is as you like, but as soon the specific WorkSpace folder is connected with Sonar cloud to the existing remote folder, it adds the json config in the vscode folder with thus:

{
	"sonarlint.connectedMode.project": {
		"connectionId": "ID",
		"projectKey": "Bla_Bla-boilerplate"
	}
}

It breaks thereafter immediately.

If I delete the json config the scanner works, but of course does not pull my custom profile set fr that project.
“Works” means it scans. It does not respect my custom profile which IS bound to that project in SonarCloud, whatsoever.
Rename class \"Admin_Notifications\" to match the regular expression ^[A-Z][a-zA-Z0-9]*$."

I changed that in my profile to:
format:^[A-Z][a-z0-9]*(_[A-Z][a-z0-9]*)*$

Clearly something is totally messed up here, and indicates an issue with SonarCloud and VSCode and nothing related to my project.
And since it appeared on the fly, the issue likely is remote (SonarCloud)

Please can you look into this?