Add CodeQL analysis workflow and update compliance pipeline schedule comment

[bschnurr]

No description provided.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[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

[bschnurr]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[rchiodo]

Copilot generated:
There is no schedule: trigger, so a branch that's quiet for weeks is never re-analyzed against newly-published CodeQL queries for newly-disclosed vulnerability classes. GitHub's default setup includes a weekly cron for exactly this. The ADO always: true change only partially mitigates this (csharp/python, not JS/TS). Consider adding a weekly schedule. (Raised by Advocate and Skeptic.) [unverified]

[verified]

[rchiodo]

Copilot generated:
There is no concurrency block, so rapid successive pushes to main spawn overlapping full analyses (each up to the 360-min timeout). Adding concurrency: { group: codeql-${{ github.ref }}, cancel-in-progress: true } would coalesce superseded runs and save runner minutes. Efficiency only, not correctness. (Advocate and Skeptic.) [unverified]

[verified]