PR Summary

This pull request includes updates to the.vsts-ci/linux.yml file, mainly focusing on modifying the paths to include and exclude for the CI pipeline. The key changes involve updating the list of paths to be included and excluded in the pipeline configuration.

Changes to CI pipeline configuration:

• Updated theinclude paths to be more specific, now including.vsts-ci/linux.yml,.vsts-ci/linux/templates/packaging.yml,assets/manpage/*,build.psm1,global.json,nuget.config,PowerShell.Common.props,src/*.csproj,tools/ci.psm1, andtools/packaging/*.
• Removed the previousexclude paths, which included various configuration files, markdown files, and other miscellaneous files.

PR Context

This pipeline used to be testing the product now it is only testing packaging, and we don't need to trigger it as much.

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: