feat: add general latency metrics

Problem:
- Soooooooooo many teams have specific latency metric fields and many are asking to add them for re-invent

Solution:
- De-dup a lot of them
e.g. amazonqGenerateApproachLatency, amazonqGenerateCodeResponseLatency, amazonqEndOfTheConversationLatency, etc

Author: jpinkney-aws

telemetry/definitions/commonDefinitions.json

@@ -997,6 +997,21 @@
             "type": "string",
             "description": "Identifies the entity within the message that user interacts with."
         },
+        {
+            "name": "clientLatency",
+            "type": "double",
+            "description": "The time duration in milliseconds to process an action on the client side"
+        },
+        {
+            "name": "serverLatency",
+            "type": "double",
+            "description": "The time duration in milliseconds to finish a request to the server side"
+        },
+        {
+            "name": "e2eLatency",
+            "type": "double",
+            "description": "The time duration in milliseconds to complete an end to end flow"
+        },
         {
             "name": "cwsprChatInteractionType",
             "allowedValues": [