Clarify request_user property description

[yihezkel]

Updated the description of the request_user property to clarify its purpose and usage in service-side diagnostic traces.

Thank you for contributing to Kusto documentation

Please add a brief comment outlining the purpose of this PR. Add links to any relevant references such as DevOps work items.

Make sure you've done the following:

1. Acrolinx: Make sure your Acrolinx score is at least 80 (higher is better) and with 0 spelling issues.

2. Successful build: Review the build status to make sure all files are green (Succeeded) and there are no errors, warnings, or suggestions.

3. Preview the pages: Click each Preview URL link, scan the entire page looking for formatting issues, in particular the parts you edited.

4. Check the Table of Contents: If you're adding a new markdown file, make sure it is linked from the table of contents.

5. Sign off: Once the PR is finalized, add a comment with #sign-off . If you need to cancel the sign-off, add a comment with #hold-off.

   NOTE: Signing off means the document can be published at any time.

Next steps

• All PRs to this repository are reviewed and merged by a human. Automatic merge is disabled on this repository for PRs, even with the qualifies-for-auto-merge label.
• Once all feedback on the PR is addressed, the PR will be merged into the main branch.

Learn more about how to contribute

[prmerger-automator]

@yihezkel : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit c6fc3c1:

✅ Validation status: passed

File	Status	Preview URL	Details
data-explorer/kusto/api/rest/request-properties.md	✅Succeeded

For more details, please refer to the build report.

[learn-build-service-prod]

Learn Build status updates of commit 4634221:

✅ Validation status: passed

File	Status	Preview URL	Details
data-explorer/kusto/api/rest/request-properties.md	✅Succeeded

For more details, please refer to the build report.

[v-regandowner]

@spelluru

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[spelluru]

#sign-off

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.