[DOCS-15219] Add Fix with Cursor remediation to Code Security docs

[thkhaha]

What does this PR do? What is the motivation?

Fixes DOCS-15219

Documents the Fix with Cursor and Copy fix prompt remediation flow across Code Security:

• Adds a Fix with Cursor section to the SAST, SCA, and IaC product pages
• Documents the Fix with Cursor link in pull request comments (SAST and code quality findings)
• Adds Cursor to the Code Security IDE plugins page
• Notes deep-link handling on the Datadog Extension for VS Code & Cursor page

Screenshots of the Remediate with AI dialog and the PR-comment link are included.

Merge instructions

Merge readiness:

• Ready for merge

Additional notes

AI-assisted draft with product screenshots. Opened as a draft pending SME technical validation before docs-team review, per the docs team's AI-content guidance. Documented as GA — to confirm with the Code Security team before merge.

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/tae-kim/code-security-fix-with-cursor/ide_plugins/vscode/
• https://docs-staging.datadoghq.com/tae-kim/code-security-fix-with-cursor/security/code_security/dev_tool_int/ide_plugins/
• https://docs-staging.datadoghq.com/tae-kim/code-security-fix-with-cursor/security/code_security/dev_tool_int/pull_request_comments/
• https://docs-staging.datadoghq.com/tae-kim/code-security-fix-with-cursor/security/code_security/iac_security/
• https://docs-staging.datadoghq.com/tae-kim/code-security-fix-with-cursor/security/code_security/software_composition_analysis/
• https://docs-staging.datadoghq.com/tae-kim/code-security-fix-with-cursor/security/code_security/static_analysis/

[github-actions]

⚠️ Possible site support note detected

The following files have a site-region shortcode at the top of the page that mentions a feature being "not available" or "not supported":

• content/en/security/code_security/static_analysis/_index.md

Are you trying to document site support for a product? If so, the site-region shortcode is not the recommended approach. See the Documenting site support guide for the preferred method.

[joepeeples]

Opened DOCS-15221 to assign a Docs writer and follow up with editorial review.

[joepeeples]

Approved with a few small, non-blocking suggestions, thanks!

[joepeeples]

Breaking up long sentence:

Suggested change

	The extension also handles the {{< ui >}}Fix with Cursor{{< /ui >}} deep link used in Code Security. When you click {{< ui >}}Fix with Cursor{{< /ui >}} in the Datadog UI or in a pull request comment, the extension opens the workspace in Cursor, checks out the relevant repository, branch, and commit, and loads a tailored remediation prompt for the finding.
	The extension also handles the {{< ui >}}Fix with Cursor{{< /ui >}} deep link used in Code Security. When you click {{< ui >}}Fix with Cursor{{< /ui >}} in the Datadog UI or in a pull request comment, the extension opens the workspace in Cursor. It then checks out the relevant repository, branch, and commit, and loads a tailored remediation prompt for the finding.

[joepeeples]

Suggested change

	You can start this flow from the {{< ui >}}Remediation{{< /ui >}} section of a vulnerability's side panel, or from the {{< ui >}}Repositories{{< /ui >}} table, where each row represents a repository or file that contains the vulnerable library.
	You can start this flow from the {{< ui >}}Remediation{{< /ui >}} section of a vulnerability's side panel, or from the {{< ui >}}Repositories{{< /ui >}} table. Each row in the table represents a repository or file that contains the vulnerable library.

[joepeeples]

The IDE Plugins landing page treats the VS Code & Cursor extension as one item, since the same extension is used for both IDEs. But if you think Cursor is a distinct enough use case, OK to leave as separate items.