PR Summary

This pull request includes several changes to enhance the configuration and pipeline scripts, primarily focusing on enabling CodeQL analysis conditionally based on the branch and improving the organization of the configuration files.

Configuration Enhancements:

• Codebase Name Addition:
  • Added codebaseName to .config/tsaoptions.json to specify the name of the codebase. ([.config/tsaoptions.jsonR2](https://github.com/PowerShell/PowerShell/pull/24278/files#diff-5087085f56036da072ca64127f12fef07158982e2572f4e072dfce97bba799e2R2))

Pipeline Script Improvements:

• Conditional CodeQL Enablement:

  • Added a new variable CODEQL_ENABLED in .pipelines/PowerShell-Coordinated_Packages-Official.yml to conditionally enable CodeQL based on the branch. ([.pipelines/PowerShell-Coordinated_Packages-Official.ymlR77-R82](https://github.com/PowerShell/PowerShell/pull/24278/files#diff-b4a2090e3664c911fbfe10b93d8703cba9141cabb8707085b1b6885a4ee8653aR77-R82))
  • Updated the codeql section in .pipelines/PowerShell-Coordinated_Packages-Official.yml to use the new CODEQL_ENABLED variable. ([.pipelines/PowerShell-Coordinated_Packages-Official.ymlR100-R103](https://github.com/PowerShell/PowerShell/pull/24278/files#diff-b4a2090e3664c911fbfe10b93d8703cba9141cabb8707085b1b6885a4ee8653aR100-R103))

• Linux Pipeline Adjustments:

  • Disabled auto-injected CodeQL enablement and added manual control in .pipelines/templates/linux.yml. ([.pipelines/templates/linux.ymlL36-R38](https://github.com/PowerShell/PowerShell/pull/24278/files#diff-d57c933d863854f9d912e16e721ee4f97370454f265d73be75d62448be712056L36-R38))
  • Updated conditions for CodeQL3000Init and CodeQL3000Finalize tasks to use CODEQL_ENABLED variable in .pipelines/templates/linux.yml. ([[1]](https://github.com/PowerShell/PowerShell/pull/24278/files#diff-d57c933d863854f9d912e16e721ee4f97370454f265d73be75d62448be712056L57-R64), [[2]](https://github.com/PowerShell/PowerShell/pull/24278/files#diff-d57c933d863854f9d912e16e721ee4f97370454f265d73be75d62448be712056L113-R115))

• Windows Pipeline Adjustments:

  • Disabled auto-injected CodeQL enablement and added manual control in .pipelines/templates/windows-hosted-build.yml. ([.pipelines/templates/windows-hosted-build.ymlL37-R39](https://github.com/PowerShell/PowerShell/pull/24278/files#diff-75adb3400c53c5cbe183c86d9d543a4cda81cd7664b45c4bf3ce77478e8ff098L37-R39))
  • Updated conditions for CodeQL3000Init and CodeQL3000Finalize tasks to use CODEQL_ENABLED variable in .pipelines/templates/windows-hosted-build.yml. ([[1]](https://github.com/PowerShell/PowerShell/pull/24278/files#diff-75adb3400c53c5cbe183c86d9d543a4cda81cd7664b45c4bf3ce77478e8ff098L58-R65), [[2]](https://github.com/PowerShell/PowerShell/pull/24278/files#diff-75adb3400c53c5cbe183c86d9d543a4cda81cd7664b45c4bf3ce77478e8ff098L187-R189))

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: