telemetry: toolkit_trackScenario #856

Problem
No generic metric for counting how many times a (potentially temporary) scenario is reached.
Such scenarios may be temporary and thus a dedicated metric is not appropriate.

Example (vscode):
When customer use workspaces to generate files, RTS and LLM cannot decide which folder to deliver the generated file. We want track how many times we reach for accountability and prioritization.

Solution
Add toolkit_trackScenario.

Author: tverney

telemetry/definitions/commonDefinitions.json

@@ -1575,6 +1575,11 @@
             ],
             "description": "Type of save executed"
         },
+        {
+            "name": "scenario",
+            "type": "string",
+            "description": "Scenarios to count in telemetry"
+        },
         {
             "name": "schemaLanguage",
             "type": "string",
@@ -6820,6 +6825,30 @@
             ],
             "passive": true
         },
+
+        {
+            "name": "toolkit_trackScenario",
+            "description": "Generic metric for tracking arbitrary scenarios that are not yet formalized into a full metric.",
+            "unit": "Count",
+            "metadata": [
+               
+                {
+                    "type": "amazonqConversationId",
+                    "required": true
+                },
+                 {
+                    "type": "count"
+                },
+                {
+                    "type": "credentialStartUrl",
+                    "required": false
+                },
+                {
+                    "type": "scenario",
+                    "required": true
+                }
+            ]
+        },
         {
             "name": "toolkit_viewLogs",
             "description": "View logs for the toolkit"
@@ -6879,4 +6908,4 @@
             ]
         }
     ]
-}
+}