PR Summary

This pull request includes changes to streamline and centralize the configuration for path filtering in GitHub Actions workflows. The most important changes involve the creation of a shared filter configuration file and the modification of multiple CI workflow files to use this shared configuration.

Centralization of path filters:

• .github/action-filters.yml: Created a new file to define shared path filters for different components like github, tools, props, tests, mainSource, and buildModule.

Updates to CI workflows:

• .github/workflows/linux-ci.yml: Updated to use the shared path filters from .github/action-filters.yml and added a step to capture outputs.
• .github/workflows/macos-ci.yml: Updated to use the shared path filters from .github/action-filters.yml and added a step to capture outputs.
• .github/workflows/windows-ci.yml: Updated to use the shared path filters from .github/action-filters.yml and added a step to capture outputs.

PR Context

The actions were overmatching after moving to dorny/paths-filters because it does a logical or of all filters including the not (!) statements.

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: