Add qualified_id field to Reporting Data Export API schema

Updates the Unstable OpenAPI spec to include the new qualified_id field
for attribute disambiguation in the get_datasets response.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: hitvardhan-solanki-ai

descriptions/0/api.intercom.io.yaml

@@ -1514,6 +1514,7 @@ paths:
                   example: conversation
                 attribute_ids:
                   type: array
+                  description: List of attribute identifiers to include in the export. Accepts either the simple id (e.g., "Brand") or the qualified_id (e.g., "people.Brand"). Use qualified_id when the same attribute name exists across different types (e.g., user and conversation custom data).
                   items:
                     type: string
                   example: [conversation_id, conversation_started_at]
@@ -1734,7 +1735,12 @@ paths:
                             properties:
                               id:
                                 type: string
+                                description: The attribute identifier. For custom attributes, this may be ambiguous if the same name exists across different attribute types (e.g., user vs conversation custom data). Use qualified_id for disambiguation.
                                 example: conversation_id
+                              qualified_id:
+                                type: string
+                                description: A namespaced identifier that uniquely identifies the attribute across all types. Format is "type.name" (e.g., "people.Brand", "conversation.Brand"). Use this when attributes have the same name across different types.
+                                example: conversation.conversation_id
                               name:
                                 type: string
                                 example: Conversation ID