fix sorting of console login telemetry definitions

Author: keenwilson

telemetry/definitions/commonDefinitions.json

@@ -144,6 +144,11 @@
             "type": "int",
             "description": "Current number of authentication connections the user has"
         },
+        {
+            "name": "authConsoleLoginStarted",
+            "type": "boolean",
+            "description": "Indicates the console login flow was initiated" 
+        },
         {
             "name": "authEnabledConnections",
             "type": "string",
@@ -185,11 +190,6 @@
             "type": "boolean",
             "description": "Whether the code issue was detected by auto-review"
         },
-        {
-            "name": "authConsoleLoginStarted",
-            "type": "boolean",
-            "description": "Indicates the console login flow was initiated" 
-        },
         {
             "name": "awsAccount",
             "type": "string",
@@ -4004,6 +4004,16 @@
                 }
             ]
         },
+        {
+            "name": "auth_consoleLoginCommand",
+            "description": "Tracks the complete console login flow, including profile creation and activation",
+            "metadata": [
+                {
+                    "type": "authConsoleLoginStarted",
+                    "required": false
+                }
+            ]
+        },
         {
             "name": "auth_signInPageClosed",
             "description": "When the Amazon Q sign in page is closed.",
@@ -4105,16 +4115,6 @@
             ],
             "passive": true
         },
-        {
-            "name": "auth_consoleLoginCommand",
-            "description": "Tracks the complete console login flow, including profile creation and activation",
-            "metadata": [
-                {
-                    "type": "authConsoleLoginStarted",
-                    "required": false
-                }
-            ]
-        },
         {
             "name": "aws_consoleLoginCLISuccess",
             "description": "Emitted when AWS CLI 'aws login' command completes successfully with exit code 0"