PR Summary

Adds the commands:

• Get-CompletionOptions
• Set-CompletionOptions

which allows the user to view and change various code completion related settings.
Currently there are 4 options available:

1: AddTrailingSeparatorForContainers (bool) which determines whether or not a separator should be added at the end of directory completions, like:gci C:\Windo<Tab> -> C:\Windows\

2: PreferredPathSeparator (Enum) which determines how to handle separators when completing file paths. There are 4 possible values:

1. Default - Current behavior where it uses the separator specified in the provider.
2. LastUsed - Uses whichever separator was last seen in the input text, or if no separator was seen, the default specified in the provider.
3. Slash - Always uses a regular slash (/)
4. Backslash - Always uses a backslash ()

3: PathSorting (Enum) which determines how path completion results are sorted. Default behavior is to sort by the full path but this can be turned off, or changed to list containers first.

4: ExcludedModules (string array) which allows users to exclude commands from certain modules from the completion results.

PR Context

Fixes#18963

As mentioned in that issue there are various user requests to change code completion behavior and some of those requests may not be suited for everyone.
We already have the "Options" hashtable inTabexpansion2 but it's not very user friendly to edit that function to change completion options you may want to change on the fly.
A point worth discussing would be if we should include the existing completion options (Include hidden fileshares, relative/full paths and literal VS normal paths).
I decided to take inspiration fromRegister-ArgumentCompleter and make these options into commands, rather than a PS variable but either option is fine by me.

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: