Collect telemetry data for comparing environments detected by legacy and new python finder

[karthiknadig]

No description provided.

[DonJayamanne]

Problems

• Counting envs by Kind in TS locator and comparing against Native locator will not work.
  E.g. /usr/bin/python could be treated as global by TS local and System by Native locator.
  This is a hypothetical example, the rules for global, unknown, system, etc are not easy and not easy to translate in new search algorithm.
• Virtual envs from other worksapce folders can end up in cache thus end up being listed by other workspace folders.
  Native Locator will never find them.
  I.e. open folder A, and that has a venv named .venvA, now close and open folder B, the env .venvA still ends up in the list of envs and this will be reported as not found by Native locator.
  thats a false positive.
• pyenv virtual envs are detected incorrectly.
  Python version is always incorrect even when clearing & reloading cachine #23661

Solutions

• Check if all exes listed by TS locator are found in the list of exes returned by Native
• Ignore pyenv virtual envs when comparing the counters

@karthiknadig /cc

[amunger]

I assume @karthiknadig or @DonJayamanne can just verify this since they will be the consumers of the telemetry