PR Summary

This pull request introduces support for a new V2 socket server mode in PowerShell's console host, along with improvements to test execution and workflow triggers. The main focus is on enabling the -V2SocketServerMode command-line parameter (Windows only), which requires a token and UTC timestamp for secure operation. Additionally, the build system and CI workflows are enhanced for better flexibility and debugging.

V2 Socket Server Mode (Windows-only enhancements)

• Added support for the -V2SocketServerMode command-line parameter, which enables a new socket server mode requiring both a token (-Token) and a UTC timestamp (-UTCTimestamp). The parser, validation logic, and server startup flow have been updated accordingly. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
• Updated HyperVSocketMediator and related client/server classes to support token-based authentication and the new session ID socket for V2 mode. [1] [2] [3] [4]

Command-line Parameter Parsing Improvements

• Extended the ParameterBitmap enum to include the new V2 socket server mode and ensured all bitmasks are properly sized for future expansion. [1] [2]
• Added error messages for missing mandatory arguments and parameters, improving user feedback when required options are omitted. [1] [2]

Build and Test System Improvements

• Enhanced the Start-PSxUnit function to support test filtering and debug logging, allowing more granular and verbose test execution. [1] [2]

CI Workflow Enhancements

• Updated GitHub Actions workflow triggers to include branches matching the *-feature pattern, ensuring feature branches are properly built and tested. [1] [2] [3]

PR Context

Already fixed in v7.5.3 and v7.4.12

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. If this PR is a work in progress, please open this as a Draft Pull Request and mark it as Ready to Review when it is ready to merge.
• 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