fix: updated sample full permissive IAM policy for AWS Batch

[mp-seqera]

Summary

This PR updates the sample full permissive IAM policy for AWS Batch based on findings from internal testing to ensure compute environments can be created successfully.

Background

During internal validation of the AWS Batch setup flow, we identified gaps in the sample IAM policy that could prevent compute environment creation and limit visibility into Batch resources.

Changes

• Added missing instance profile resource scope - Updated the policy to include permissions for instance-profile resources required during compute environment creation.
• Corrected resource scoping for Batch list APIs - Moved the following actions to use wildcard (*) resources, as they are list-style operations: batch:DescribeComputeEnvironments and batch:DescribeJobQueues
• Refined the sample policy - Ensures the example policy is fully permissive and functions as expected during end-to-end Batch provisioning.

Impact

• Improves reliability of compute environment creation during setup.
• Aligns the sample policy with AWS IAM best practices for list and describe actions.
• Reduces friction when validating AWS Batch configurations.

[netlify]

✅ Deploy Preview for seqera-docs ready!

Name	Link
🔨 Latest commit	52de5c9
🔍 Latest deploy log	https://app.netlify.com/projects/seqera-docs/deploys/696e5683827525000903e6a5
😎 Deploy Preview	https://deploy-preview-1012--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]

Follow up of #943 and #941

[justinegeffen]

Some editorial suggestions but approving so as not to block merge. Thank you!!

[bebosudo]

I backported all updates to enterprise docs down to v24.1 (which is missing a section in the nextflow troubleshooting page, hence the last commit).
In doing so I also fixed some references in the v24.x docs which were using "Studios" in the name instead of "Data Studios", the previous naming.
The aws batch CE docs are now mostly identical: the cloud version mentions that the TowerForge- prefix can't be edited, while the enterprise releases mention it; the v24.x docs also use old naming "Data Studios".

[alberto@notfedora]$ diff platform-cloud/docs/compute-envs/aws-batch.md platform-enterprise_docs/compute-envs/aws-batch.md
333c333
< The quick start policy is expecting CE and JQ names automatically created by Seqera to start with the `TowerForge-` prefix, which is the default prefix used by Platform Cloud resources and can't be customized.
---
> The quick start policy is expecting CE and JQ names automatically created by Seqera to start with the `TowerForge-` prefix, which is the default prefix used by Platform Enterprise. If you [customized it on your Enterprise installations](../enterprise/configuration/overview#compute-environments) with `TOWER_FORGE_PREFIX` adapt the policy to the new prefix.
478c478
< The quick start policy is expecting role names automatically created by Seqera to start with the `TowerForge-` prefix, which is the default prefix used by Platform Cloud resources and can't be customized.
---
> The quick start policy is expecting role names automatically created by Seqera to start with the `TowerForge-` prefix, which is the default prefix used by Platform Enterprise. If you [customized it on your Enterprise installations](../enterprise/configuration/overview#compute-environments) with `TOWER_FORGE_PREFIX` adapt the policy to the new prefix.
906c906
< 1. After logging in to [Seqera](https://cloud.seqera.io) and selecting a workspace from the dropdown menu at the top of the page, select **Compute environments** from the navigation menu.
---
> 1. After logging in to your Seqera installation and selecting a workspace from the dropdown menu at the top of the page, select **Compute environments** from the navigation menu.

I'll merge this now. Thanks for reporting this @mp-seqera!