Fix: Update JSON threat protection sequence editing steps [4.0.0]

[wso2-engineering-bot]

This PR was automatically generated by Claude AI.

• Issue: Editing JSON threat protection sequence steps should be fixed. #10709
• Type: Documentation
• Summary: Updated the "Editing the sequence through registry artifacts" and "Applying the JSON validator policy" sections to reflect the correct process for APIM 4.0.0. Removed references to non-existent Management Console path /_system/governance/apimgt/customsequences and updated to use the Publisher Portal policies approach as shown in version 4.3.0.
• Style Scope Verification: Microsoft Style Guidelines have been applied ONLY to newly added content without modifying existing content style unless specifically requested.
• Verification: mkdocs build encountered Python compatibility issues with mkdocs 1.0.4 on Python 3.12, but changes match the verified correct version 4.3.0 documentation structure.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fixing-issue-10709-4.0.0-1771220513

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}