this is the implementation of https://github.com/PowerShell/PowerShell-RFC/blob/249e8d88eb779a6003fd138609ae94417ae13698/2-Draft-Accepted/RFC0036-AdditionalTelemetry.md

PR Summary

• Add Telemetry in the following areas
  • When execution occurs, the ApplicationType will be captured as a metric
  • When a module is loaded, capture a metric of the module name if it's in the allow list.
  • When PowerShell.Create is used, send a metric
  • When an experimental feature is activated send a metric (this is at startup only)
  • Update startup telemetry to measure the type of shell startup (remote/ssh)
• Added a couple of new fields to the StartUp telemetry
  • Channel allows us to understand when PS is being used in a docker instance and what the OS is.
  • Added a unique identifier which allows us to determine unique users. It's a generated guid which is persisted to disk.
  • Added a unique identifier for the shell session

I added an internal member to System.Management.Automation.Platform called CacheDirectory which makes it easy to find the location of the cache directory. I think this should probably be public, but that can be decided at a later time.

PR Context

We knew that our initial telemetry was just that. The bare minimum of information to determine whether the shell was actually being used and on what platform. The additional information we think we need is captured in the RFC.

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).