Warn that data connector header values are logged unmasked

descriptions/0/api.intercom.io.yaml

@@ -44629,7 +44629,8 @@ components:
           - visitors
         headers:
           type: array
-          description: HTTP headers to include in the request.
+          description: |
+            HTTP headers to include in the request. Don't put credentials such as API keys here: header values are recorded unmasked in the connector's execution logs, except `Authorization`, which is always masked. Attach a stored credential with `token_ids` instead (see [Create an auth token](/docs/references/preview/rest-api/api.intercom.io/auth-tokens/createauthtoken)). Its value is stored encrypted, masked in execution logs, and never returned.
           items:
             type: object
             properties:
@@ -44807,7 +44808,8 @@ components:
           - users
         headers:
           type: array
-          description: HTTP headers to include in the request.
+          description: |
+            HTTP headers to include in the request. Don't put credentials such as API keys here: header values are recorded unmasked in the connector's execution logs, except `Authorization`, which is always masked. Attach a stored credential with `token_ids` instead (see [Create an auth token](/docs/references/preview/rest-api/api.intercom.io/auth-tokens/createauthtoken)). Its value is stored encrypted, masked in execution logs, and never returned.
           items:
             type: object
             properties:

descriptions/2.16/api.intercom.io.yaml

@@ -30668,7 +30668,8 @@ components:
           - visitors
         headers:
           type: array
-          description: HTTP headers to include in the request.
+          description: |
+            HTTP headers to include in the request. Don't put credentials such as API keys here: header values are recorded unmasked in the connector's execution logs, except `Authorization`, which is always masked. Attach an authentication token with `token_ids` instead; its value is masked in execution logs.
           items:
             type: object
             properties:
@@ -30794,7 +30795,8 @@ components:
           - users
         headers:
           type: array
-          description: HTTP headers to include in the request.
+          description: |
+            HTTP headers to include in the request. Don't put credentials such as API keys here: header values are recorded unmasked in the connector's execution logs, except `Authorization`, which is always masked. Attach an authentication token with `token_ids` instead; its value is masked in execution logs.
           items:
             type: object
             properties:

descriptions/2.17/api.intercom.io.yaml

@@ -39366,7 +39366,8 @@ components:
           - visitors
         headers:
           type: array
-          description: HTTP headers to include in the request.
+          description: |
+            HTTP headers to include in the request. Don't put credentials such as API keys here: header values are recorded unmasked in the connector's execution logs, except `Authorization`, which is always masked. Attach an authentication token with `token_ids` instead; its value is masked in execution logs.
           items:
             type: object
             properties:
@@ -39506,7 +39507,8 @@ components:
           - users
         headers:
           type: array
-          description: HTTP headers to include in the request.
+          description: |
+            HTTP headers to include in the request. Don't put credentials such as API keys here: header values are recorded unmasked in the connector's execution logs, except `Authorization`, which is always masked. Attach an authentication token with `token_ids` instead; its value is masked in execution logs.
           items:
             type: object
             properties: