APPSINTG-254: Added cyberark epm ispss private preview

[piyushgupta-sumo]

Purpose of this pull request

This pull request contains private preview for cyberark EPM ISPSS auth

Select the type of change

• Minor Changes - Typos, formatting, slight revisions
• Update Content - Revisions, updating sections
• New Content - New features, sections, pages, tutorials
• Site and Tools - .clabot, version updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Ticket (if applicable)

APPSINTG-254

[amee-sumo]

This appears to conflict directly with #7027 (same ticket, same author, opened a day earlier — still open).

#7027 edits the existing cyberark-source.md in place to describe this exact same ISPSS 2.0.0 migration, but frames it as already GA: "we have released version 2.0.0..." with a public legacy-auth deprecation deadline of December 31, 2026.

This PR adds a separate page (cyberark-source-beta.md) with the same auth model swap, same config fields, same deprecation notice/date — but framed as Private Preview, gated behind contacting an account rep.

I diffed the two against the current live doc: aside from the GA vs. private-preview framing (noindex/preview badge here vs. none in #7027), the content is otherwise identical. Both can't be right at the same time — if ISPSS 2.0.0 is actually still private-preview-only, #7027 shouldn't be shipping a public hard-cutover date for a replacement most customers can't access yet. If it's GA, this PR is redundant.

Since both PRs are still open, whichever merges second will conflict with or silently undo the other's framing. Could we get confirmation on which is accurate (GA or private preview) before either merges, and close/update the other accordingly?

[amee-sumo]

Pulled the latest changes — a couple of follow-ups:

1. The GA vs. Private Preview conflict with #7027 is still unresolved. The new commit creates separate example-private.json/example-private.tf files instead of reusing the shared example.json/example.tf that #7027 also edits — that avoids a git merge conflict, but doesn't address the actual content conflict (both PRs still describe the same ISPSS 2.0.0 migration with opposite availability framing).

2. New bug: static/files/c2c/cyberark/example-private.json is invalid JSON. Validated it directly and got:

Expecting property name enclosed in double quotes: line 14 column 5 (char 417)

• Trailing comma after "policy_audit_raw_events": false, right before the closing }.
• Missing schemaRef, aggregated_events, and polling_interval — all present correctly in the sibling example-private.tf, and schemaRef/polling_interval are marked Required: Yes in this page's own JSON schema table.

A customer copy-pasting this file as-is will hit a parse error.

[amee-sumo]

The JSON bug is fixed — verified example-private.json is now valid and includes schemaRef, aggregated_events, and polling_interval.

Approving on that basis. Note the structural concern from earlier in this thread is still open: this page frames the ISPSS 2.0.0 migration as Private Preview while #7027 frames the identical change as GA on the live cyberark-source.md. That should get reconciled between the two PRs before/alongside merge.