A/B experiment for partial activation and CMakeLists present anywhere in the folder: quickPick one of existing CMakeLists versus "Create/Locate/Ignore" popup

[andreeis]

This A/B experiment is designed for cmake-tools users who are working in a partially activated workspace with a CMakeLists.txt file somewhere in the active folder.

Group A (control)

• Users working in a partially activated workspace with a CMakeLists.txt file somewhere in the active folder are prompted with a toast notification (current behavior – just need to add telemetry).
  Group B (treatment)
• Users working in a partially activated workspace with a CMakeLists.txt file somewhere in the active folder are prompted to select their root CMakeLists.txt from a list in the command palette as soon as cmake-tools activates (even if they don’t have an active kit or Configure Preset).

The new feature introduced by the experiment is tracked here: #533.
The corresponding telemetry is tracked here: #1901.

Below are more details on the required telemetry that we need to add.

Shared telemetry (used by both the treatment and the control)
• A new property (bool) on the existing ms-vscode.cmake-tools/open event that indicates whether the folder is fully or partially activated
• A new property (bool) on the existing ms-vscode.cmake-tools/open event that indicates whether the folder contains a CMakeLists.txt file (at any level)

Control telemetry
• A new event that fires when the toast notification appears (“CMakeLists.txt was not found at the root of the folder… How would you like to proceed?”)
• A new event that fires when the user interacts with the toast notification (dismisses it, create, locate, or do not show again)

Treatment telemetry
• A new event that fires when the user is prompted to select a CMakeLists.txt from the command palette
• A new event that fires when the user interacts with the prompt (dismisses it or selects a CMakeLists.txt)