SCANPY-201 Enable analysis on both SQC instances

[Wohops]

SCANPY-201

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqube-cloud-us]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Wohops]

@ghislainpiot there are 3 commits:

1. ca55bac is setting the "simplest" configuration I could think about. While running analysis on each PR so we can see it works. Above, you can see outcomes of the 3 instances reporting on the PR.
2. 0d2847a is fixing a weird behavior when setting as host https://sonarqube.us (see ticket SCANPY-203)
3. d07dd29 only runs the analysis to CRON and master branch

⚠️ Please keep the commits separated when merging and rebase.

[ghislainpiot]

I left very small comments, it is up to you to do the changes or not.

I have a bigger concern: if there is no issue synchronization, does that mean we might get Slack messages everyday?

[ghislainpiot]

I had another look and I think it makes no sense to block, there is only one issue on the project and no hotspots

[sonarqube-next]

Quality Gate passed for 'Python Scanner'

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
No data about Duplication

See analysis details on SonarQube