chore(ci): remove SonarCloud CI-based analysis to enable Automatic Analysis

[mzner]

Description

Remove CI-based SonarCloud analysis from GitHub Actions workflows to enable SonarCloud's Automatic Analysis mode via the GitHub App integration. This eliminates the need for a SONAR_TOKEN secret in CI runners.

Related Issue

• N/A

Motivation and Context

SonarCloud's Automatic Analysis mode provides static analysis without requiring a token in CI. This reduces secret exposure surface in GitHub Actions and simplifies the workflow. Coverage data is no longer uploaded automatically, but static analysis (bugs, code smells, security hotspots) continues via SonarCloud's own infrastructure.

How Has This Been Tested?

• test environment: GitHub Actions workflow syntax validation
• test case 1: Verified _build.yml and test.yml are valid YAML after changes
• test case 2: Automatic Analysis toggle becomes available on SonarCloud after merge

[update-docs]

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.

[kw-security]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[awabcodes]

Please remove passing of the token in the nightly workflow as well