SONAR-25652 Migrate to GitHub actions

[jCOTINEAU]

SONAR-25760

below comment is by @lukasz-jarocki-sonarsource :
Build and push to Azure and Google Cloud Platform were validated before moving this pull request to "in review".

I couldn't find out how we often/when we run Azure push to staging on Cirrus, so for now I keep it only as workflow dispatch.

[sonarqube-next]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[sonarqube-next]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
1 Accepted issue

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
0.1% Duplication on New Code

See analysis details on SonarQube

[carminevassallo]

Thanks @jCOTINEAU and @lukasz-jarocki-sonarsource, this is simply great!

Before accepting, I think we still need to define the required checks or an aggregator of them. Specifically, in the migrations of the repos belonging to our squad, we are trying to use the concept of qa-validator (see this example) to ensure that all the required checks are considered in the validation and we mark as required just the qa-validator task. Would it be possible to add it?

Also, I noticed we are not using the latest slack notification action. I'm fine with not having it added now, we will tackle it here: https://sonarsource.atlassian.net/browse/SONAR-26397.

[lukasz-jarocki-sonarsource]

thanks for the review, feel free to add qa-validator, in case you won't have time for it I will take a look at it later this week :)

[sonarqube-next]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
0.1% Duplication on New Code

See analysis details on SonarQube

[carminevassallo]

I've just added the missing qa-validator (which is now required) and fixed the quality-gate issues.