chore: AWS Batch guide in enterprise shouldn't mention logging in to seqera cloud

[bebosudo]

I also noticed a line was removed from vNext and v25.3, so I removed it from all v25 docs: https://github.com/seqeralabs/docs/pull/953/files?w=1#r2773192505

[netlify]

✅ Deploy Preview for seqera-docs ready!

Name	Link
🔨 Latest commit	348dd55
🔍 Latest deploy log	https://app.netlify.com/projects/seqera-docs/deploys/6985c20077ab48000839e18f
😎 Deploy Preview	https://deploy-preview-1111--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.

[gavinelder]

Given this is a back-port I'm approving to unblock and improve.

However this feels like it would benefit from platform-agnostic language that does not assume a specific installation kind to limit divergence between cloud vs enterprise.

The "After logging in" preamble feels redundant since accessing any part of the application already implies authentication, by assuming users are already authenticated we can jump straight to the relevant navigation steps or permission requirements.

In the future I would recommend defaulting to something like:

• "From the Seqera console"
• "With a user with admin permissions in the workspace"
• "Inside Seqera"

IMHO Cloud & Enterprise docs should be 1 for 1 in terms of Style , language and content with only the content for Installation and configuration of the installation diverging.

Personally I would not want to mention special overrides which can be done by an administrator to alter a Seqera product experience outside of the installation boundary.