docs(compute-envs): make IAM policies downloadable and source from JSON files

[gavinelder]

Summary

Refactors the inline IAM policy <details> blocks on the AWS compute environment pages (platform-cloud) so they are:

• Sourced from a single canonical JSON file per policy (no more 200-line JSON snippets pasted into Markdown).
• Downloadable — each block now has a Download <name>.json link next to the rendered code, served by Docusaurus as a fingerprinted asset.
• Always in sync — the expanded code block and the download link both come from the same file, so they can't drift.

Pages migrated

Page	Policies extracted
compute-envs/aws-batch.mdx (was .md)	Full permissive policy
compute-envs/eks.mdx (was .md)	Full permissive policy
compute-envs/aws-cloud.mdx (was .md)	Full permissive policy + Seqera Intelligent Compute policy

New JSON sources live under platform-cloud/docs/compute-envs/_policies/. The _ prefix keeps Docusaurus from treating them as standalone pages.

Drive-by fix

The Seqera Intelligent Compute policy in aws-cloud.md had a duplicate "Action": [ line (previously L526-527), making the JSON invalid. The downloadable version is now valid — and tabs are normalized to spaces.

How it works

Rspack's built-in ?raw import bypasses the JSON parser and gives us the file contents as a string:

import AwsBatchFullPolicy from './_policies/aws-batch-full-policy.json?raw';

<details>
<summary>Full permissive policy (for reference)</summary>

<CodeBlock language="json">{AwsBatchFullPolicy}</CodeBlock>

[Download aws-batch-full-policy.json](./_policies/aws-batch-full-policy.json)
</details>

Note: The existing repo pattern (!!raw-loader!./file.yaml in seqerakit/templates.mdx) doesn't work for .json because Rspack's built-in JSON parser intercepts first. ?raw is the working pattern for JSON.

Out of scope (intentional)

• The parallel pages in platform-enterprise_docs/compute-envs/ (aws-batch.md, eks.md, aws-cloud.md) still use the old inline-JSON pattern. They have the same broken SIC JSON. Will follow up in a separate PR.
• gke.md's <details> block is shell commands + prose, not a JSON policy — left alone.
• Versioned enterprise docs (platform-enterprise_versioned_docs/version-25.3/...) are frozen, untouched.

Test plan

• yarn build succeeds, no new warnings introduced.
• All 4 JSON files parse with python3 -m json.tool.
• Built HTML for /platform-cloud/compute-envs/aws-batch/, /eks/, and /aws-cloud/ contains the expanded JSON content plus a fingerprinted asset URL (/assets/files/<name>-<hash>.json).
• Netlify preview: open each of the three pages, expand the <details> block, verify rendered JSON matches and the download link returns a valid .json file.
• Spot-check that nothing else in the docs deep-links to compute-envs/aws-batch.md/eks.md/aws-cloud.md with the .md extension (resource-labels was the only known offender and is fixed here).

🤖 Generated with Claude Code

[netlify]

✅ Deploy Preview for seqera-docs ready!

Name	Link
🔨 Latest commit	0804049
🔍 Latest deploy log	https://app.netlify.com/projects/seqera-docs/deploys/6a0f42d179d23400085ae437
😎 Deploy Preview	https://deploy-preview-1434--seqera-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[bebosudo]

I restarted the netlify deployment which ran out of memory on the first try.
The change looks good to me: https://deploy-preview-1434--seqera-docs.netlify.app/platform-cloud/compute-envs/aws-batch#required-platform-iam-permissions

[MichaelTansiniSeqera]

Nice.

Could we rename the section to something like 'Example IAM Policies' for clarity?

Also as Intelligent Compute is not yet released, can we exclude it from the release or hide it? @justinegeffen

[gavinelder]

@MichaelTansiniSeqera there was a discussion around Intelligent compute and the decision was to include it with an Alpha / Early Access preview admonition and to speak to an account manager around interest.

Will see how "Default / Example Iam works"

[christopher-hakkaart]

fix formatting

[justinegeffen]

@copilot resolve the merge conflicts in this pull request

[Copilot]

@copilot resolve the merge conflicts in this pull request

Merge conflicts resolved in commit 0804049. The conflict was in aws-cloud.mdx — origin/master had a fix (2eb2dd30) removing a duplicate "Action": [ line from the inline JSON, while our branch had already extracted that policy to _policies/aws-cloud-intelligent-compute-policy.json (without the duplicate) using the <CodeBlock> approach. Kept our version.

[justinegeffen]

@gavinelder, I've merged this but wanted to check if we should replicate the changes in the enterprise docs?