SCCPPGHA-6 Support Running on Linux ARM64

[friedbyalice]

List of checkpoint to verify/do before merging a PR.

Dev checklist

• Write/update tests
• Functional validation
• Public documentation update
• Private documentation update
• Clean commits (should start with a ticket number, clear message, no fixup, wip)
• Maximize code coverage as much as possible

---

Reviewer checklist

• Code review
• Functional validation
• Check commits are clean

---

Steps to validate this PR

Fill-in how you performed the validation, and how the reviewer can replicate it:

• Added tests for the configure_paths script that check the newly introduced SONAR_SCANNER_URL_UNIVERSAL and SONAR_SCANNER_SHA_UNIVERSAL variables, and the variations on the other variables when running on Linux ARM64
• Setup a repository from sonarsource-cfamily-examples with self-hosted runners (x64 and ARM64), to test that everything works on ARM64, and that java is fetched only for Linux ARM64 (the arm runner does not have java installed) run here

[friedbyalice]

Currently there are no github hosted linux arm64 runners, which makes testing difficult, but a setup with self hosted runners was made on here

[guillem-bartrina-sonarsource]

Minor comments.

But more importantly, it is worth mentioning that this PR also updates the sonar-scanner version somewhere, so we have improved traceability.

[7PH]

LGTM, with functional validation using self-hosted runners:

• ARM64 / Debian 12 (scaleway)
• X64 / Debian 11 (local)

I see there is a ticket blocking this one on Jira about updating the SonarCloud C++ tutorials to the new syntax, let me know if you want a review there as well!

[7PH]

I see that this pull request upgrades the sonar-scanner to v6, but the other PR does as well.

I think it is a good idea to separate the scanner bump in a different commit (as you did with the other PR), is it possible to split the work in 2 commits? (Could be in this PR or we can keep the other PR as well)