Clarify Egress Docs (#1399)

## Overview
It is unclear that traces are not customer traces, but operational
metadata

## Type of change

**Type:** [Replace with: New documentation page / Update existing
documentation / Fix typo/bug/link/formatting / Remove outdated content /
Other]

## Related issues/PRs
<!-- 
Link to related issues, feature PRs, or discussions (if applicable)

To automatically close an issue when this PR is merged, use closing
keywords:
- "closes #123" or "fixes #123" or "resolves #123"

For regular references without auto-closing, just use:
- "#123" or "See issue #123"

Examples:
- closes #456 (will auto-close issue #456 when PR is merged)
- See #789 for context (will reference but not auto-close issue #789)
-->
- GitHub issue:
- Feature PR:

<!-- For LangChain employees, if applicable: -->
- Linear issue:
- Slack thread:

## Checklist
<!-- Put an 'x' in all boxes that apply -->
- [ ] I have read the [contributing guidelines](README.md)
- [ ] I have tested my changes locally using `docs dev`
- [ ] All code examples have been tested and work correctly
- [ ] I have used **root relative** paths for internal links
- [ ] I have updated navigation in `src/docs.json` if needed
- I have gotten approval from the relevant reviewers
- (Internal team members only / optional) I have created a preview
deployment using the [Create Preview Branch
workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml)

## Additional notes
<!-- Any other information that would be helpful for reviewers -->

Author: romain-priour-lc

src/langsmith/self-host-egress.mdx

@@ -42,7 +42,7 @@ As of version ***0.11***, LangSmith deployments will by default send telemetry d
 
 * **Request metadata**: anonymized request counts, sizes, and durations.
 * **Database metrics**: query durations, error rates, and performance counters.
-* **Distributed traces**: end-to-end traces with timing and error information for high-latency or failed requests.
+* **Operational LangSmith traces**: traces with timing and error information for high-latency or failed requests. These are **not** customer traces, these are operational traces about the functioning of the LangSmith instance.
 
 <Info>
 We do not collect actual payload contents, database records, or any data that can identify your end users or customers.
@@ -123,7 +123,7 @@ In an effort to maximize transparency, we provide sample payloads here:
 }
 ```
 
-### Telemetry: Metrics
+### Telemetry: Operational LangSmith Metrics
 
 **Endpoint:**
 
@@ -214,7 +214,7 @@ In an effort to maximize transparency, we provide sample payloads here:
 }
 ```
 
-### Telemetry: Traces
+### Telemetry: Operational LangSmith Traces
 
 **Endpoint:**