Additional Microsoft Modules to track in PS7 Telemetry

[SydneyhSmith]

PR Summary

This adds additional Microsoft-owned modules to be tracked at load time in the PowerShell 7 telemetry.

PR Context

This allows us to better understand how PowerShell is being used to manage services and to better understand the types of PowerShell users based on which modules are loaded into PowerShell sessions.

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 enumerated concerns in the summary. This may include:
    • Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
    • Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
    • Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
    • Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[SteveL-MSFT]

@joeyaiello needs to review this list for accuracy

[TravisEz13]

@SteveL-MSFT does this need to get in the RC?

[SteveL-MSFT]

@TravisEz13 yes

[joeyaiello]

Whew. Finally got through this one.

We have lots of work to do in renaming Windows PowerShell modules in the Microsoft Docs, @sdwheeler, I took some notes along the way.

[joeyaiello]

Not us, please remove

[SteveL-MSFT]

Ok from me once @joeyaiello approves

[adityapatwardhan]

@SteveL-MSFT @joeyaiello Please re-review.

[joeyaiello]

Thanks for the changes. Approving operating under the assumption that this list is not case sensitive (assuming that's what StringComparer.OrdinalIgnoreCase does, but I never can remember the exact behavior around ordinal vs. non-ordinal).

If it is case-sensitive, I have to make some more changes ASAP

[ghost]

🎉v7.0.0-rc.1 has been released which incorporates this pull request.:tada:

Handy links:

• Release Notes