PR Summary

This pull request introduces several changes to the .pipelines/apiscan-gen-notice.yml and .pipelines/templates/compliance/apiscan.yml files to incorporate CodeQL scanning capabilities. The most important changes include adding parameters for enabling CodeQL, configuring CodeQL-related variables, and integrating CodeQL tasks into the pipeline.

CodeQL Integration:

• .pipelines/apiscan-gen-notice.yml: Added a FORCE_CODEQL parameter to enable CodeQL scanning and set its cadence to 1 hour.
• .pipelines/apiscan-gen-notice.yml: Configured variables to enable or disable CodeQL based on the branch or FORCE_CODEQL parameter.
• .pipelines/apiscan-gen-notice.yml: Updated the codeql section under globalSdl to use the new CODEQL_ENABLED variable.

Pipeline Task Updates:

• .pipelines/templates/compliance/apiscan.yml: Added Codeql.SourceRoot variable to the job configuration.
• .pipelines/templates/compliance/apiscan.yml: Introduced CodeQL3000Init and CodeQL3000Finalize tasks to initialize and finalize CodeQL scanning around the build step. [1] [2]

PR Context

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Experimental feature(s) needed
    • Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    - [ ] Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:
    • Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
      (which runs in a different PS Host).
      • Issue filed:
    • Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
      • Issue filed:
    • Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
      • Issue filed:
    • Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).
      • Issue filed: