PR Summary

This pull request introduces a new parameter,SkipVerifyPackages, to the pipeline configuration files to allow skipping the verification of package licenses. The changes are primarily focused on the addition of this parameter and the conditional logic to handle it.

Pipeline Configuration Enhancements:

• AddedSkipVerifyPackages parameter to.pipelines/apiscan-gen-notice.yml to control the skipping of package verification.
• Updated theextends section in.pipelines/apiscan-gen-notice.yml to pass theSkipVerifyPackages parameter to the compliance template.
• Introduced theSkipVerifyPackages parameter in.pipelines/templates/compliance/generateNotice.yml to be used within the compliance jobs.
• Added a condition to skip the package verification step in thegenerateNotice job based on theSkipVerifyPackages parameter.
• Removed unnecessary blank lines in thegenerateNotice job script.

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 notWork in Progress.
  • If the PR is work in progress, please add the prefixWIP: or[ WIP ] to the beginning of the title (theWIP bot will keep its status check atPending 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 onPowerShell Editor Services which is used in thePowerShell 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 onPSScriptAnalyzer (which provides linting & formatting in the editor extensions).
      • Issue filed:
    • Impact onEditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).
      • Issue filed: