docs: add PowerShell tab for az resource patch command in change streams

[wttat]

Problem

The az resource patch command in the Change Streams article uses Bash-style JSON escaping (\"), which does not work in PowerShell. PowerShell handles quote escaping differently, causing the command to fail when users copy-paste it directly.

Fix

Added a tabbed section (Bash / PowerShell) so users on either shell get the correct command syntax:

• Bash: keeps the existing \"...\" escaping (unchanged)
• PowerShell: uses single-quoted string with '\\\" escaping that PowerShell handles correctly

Document

• URL: https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/vcore/change-streams
• Source: articles/documentdb/change-streams.md

[prmerger-automator]

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

[learn-build-service-prod]

Learn Build status updates of commit 44cfab3:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/documentdb/change-streams.md	✅Succeeded

For more details, please refer to the build report.

[Copilot]

Pull request overview

This PR updates the Change Streams documentation to provide shell-specific az resource patch examples so users can successfully enable the ChangeStreams preview feature when copy/pasting commands.

Changes:

• Adds tabbed Markdown content for Bash and PowerShell variants of the az resource patch command.
• Keeps the existing Bash example unchanged and introduces a PowerShell-specific quoting variant.

[Copilot]

The PowerShell example passes an invalid JSON string to --properties. Because the argument is wrapped in single quotes, the \" sequences are preserved and az receives {\"previewFeatures\": ...}, which isn't valid JSON (it starts with a backslash outside a JSON string). Use a PowerShell-safe quoting approach that results in {"previewFeatures": ["ChangeStreams"]} being passed to the CLI (for example, single quotes around a JSON string that contains unescaped double quotes).

Suggested change

	az resource patch --ids "/subscriptions/<subscription_id>/resourceGroups/<resource_group_name>/providers/Microsoft.DocumentDB/mongoClusters/<cluster-name>" --api-version 2024-10-01-preview --properties '{\"previewFeatures\": [\"ChangeStreams\"]}'
	az resource patch --ids "/subscriptions/<subscription_id>/resourceGroups/<resource_group_name>/providers/Microsoft.DocumentDB/mongoClusters/<cluster-name>" --api-version 2024-10-01-preview --properties '{"previewFeatures": ["ChangeStreams"]}'

[Copilot]

The tabbed content block (tab headers, code fences, and the terminating ---) isn't indented under step 3, so it will render outside the numbered list item and can break the step formatting. Indent the entire tabbed block to nest it under the 3. list item (consistent with other docs that use tabs inside lists).

Suggested change

	# [Bash](#tab/bash)
	```bash
	az resource patch --ids "/subscriptions/<subscription_id>/resourceGroups/<resource_group_name>/providers/Microsoft.DocumentDB/mongoClusters/<cluster-name>" --api-version 2024-10-01-preview --properties "{\"previewFeatures\": [ \"ChangeStreams\"]}"
	```
	# [PowerShell](#tab/powershell)
	```powershell
	az resource patch --ids "/subscriptions/<subscription_id>/resourceGroups/<resource_group_name>/providers/Microsoft.DocumentDB/mongoClusters/<cluster-name>" --api-version 2024-10-01-preview --properties '{\"previewFeatures\": [\"ChangeStreams\"]}'
	```
	---
	# [Bash](#tab/bash)
	```bash
	az resource patch --ids "/subscriptions/<subscription_id>/resourceGroups/<resource_group_name>/providers/Microsoft.DocumentDB/mongoClusters/<cluster-name>" --api-version 2024-10-01-preview --properties "{\"previewFeatures\": [ \"ChangeStreams\"]}"

PowerShell

az resource patch --ids "/subscriptions/<subscription_id>/resourceGroups/<resource_group_name>/providers/Microsoft.DocumentDB/mongoClusters/<cluster-name>" --api-version 2024-10-01-preview --properties '{\"previewFeatures\": [\"ChangeStreams\"]}'

---

[ttorble]

@AvijitkGupta

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