Thanks for the detailed logs.
I reproduce that same error 100% of the times when I try to scan the repo locally with an empty token, like -Dsonar.login= instead of -Dsonar.login=somecooltoken.
When the token is invalid or the user don’t have the permission, the error is different.
We may have some room to improvement here, to given an appropriate message instead of that exception. I’ll report taht internally for improvement, but of course it won’t solve your issue.
You probably still have some issue on your build configuration.
The recommended way to configure the access token, is now to use an environment variable named SONAR_TOKEN, instead of the sonar.login property than can print tokens clearly in the logs. It is automatically picked by the scanner, the -Dsonar.login=xxx part of the command should be completely removed. Could you try that?