ci: stop blocking on Sonar quality gate

[aksOps]

What changed

Remove sonar.qualitygate.wait and its timeout from the scanner configuration.

Why

PR #20 successfully reduced Sonar to one workflow running on pull requests and main. The merged main run completed analysis and uploaded commit cf31a7bf, then failed because the scanner was configured to synchronously enforce the Sonar quality gate. The gate currently reports a new-code security rating of B from two Sonar findings. That policy result is separate remediation work and should remain visible in Sonar without turning a successful scan into a ten-minute GitHub Actions failure.

This matches the official SonarQube action quick-start: run the scanner and let Sonar report analysis status independently.

Validation

• Actionlint passed
• immutable action pin check passed
• git diff --check passed
• confirmed failed main run completed analysis and uploaded the exact merge commit before quality-gate enforcement returned exit code 3

[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