docs: Fix XSS vulnerability in JSON-LD guide example

[TechManTejas]

Problem

The JSON-LD documentation example uses dangerouslySetInnerHTML with JSON.stringify() without proper escaping, creating an XSS vulnerability. Malicious content in product data (e.g., product.name containing </script><script>alert(1);</script>) could break out of the script tag and execute arbitrary JavaScript.

Solution

• Added escapeJsonForScript() helper function that escapes < and > characters using Unicode escape sequences
• Added security warning in documentation explaining the XSS risk
• Added comment reminding developers to sanitize user data
• Maintained example simplicity while making it secure

Security Impact

This change prevents potential XSS attacks that could occur when user-controlled data is included in JSON-LD structured data without proper escaping.

Testing

• Verified the escaped JSON is still valid JSON-LD
• Confirmed malicious payloads are properly escaped
• Documentation renders correctly

Fixes: XSS vulnerability in JSON-LD documentation example

[changeset-bot]

⚠️ No Changeset found

Latest commit: a54b9f3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ijjk]

Allow CI Workflow Run

• approve CI run for commit: a54b9f3

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

[stefanprobst]

i think this has been addressed in #79627

[TechManTejas]

Yup