docs: Add Wave api rate limit guide

[christopher-hakkaart]

• Add Wave api rate limit guide

Netlify preview is here: https://deploy-preview-845--seqera-docs.netlify.app/wave/nextflow/reduce-api-calls

Note: I don't love the location in the sidebar, but I think it's acceptable while we consider how guides might be presented in the docs moving forward.

[gwright99]

Why not? Let's give them a reason (i.e. requires tinkering with Batch instances to authenticate to non-ECR registry).

[gwright99]

Oh, I see you did it below. nevermind.

[adamrtalbot]

I might be tempted to generalise it to say "use the native cloud container registry", which has all the same benefits.

[christopher-hakkaart]

I've softened to "Not recommended: External container registries for AWS Batch workloads" as per your other suggestion.

Are you suggesting we don't specifically call out AWS? And just refer to "native cloud container registries" instead of "AWS Batch workloads" for both recommended and not recommended?

[adamrtalbot]

Needs a bit more precision around the language of manfiest vs layers, and when you access the Wave service.

[adamrtalbot]

I might be tempted to generalise it to say "use the native cloud container registry", which has all the same benefits.

[christopher-hakkaart]

Thanks everyone - sorry for all the noise on the PR.

I've made the suggested changes, and a larger restructure after Adams' comments made me realize we had sections that were largely similar (Building without Wave freeze, Building with Wave freeze, First pipeline run, and Subsequent pipeline runs).

This has now been shaped into two sections (Building without Wave freeze and Building with Wave freeze).

There are two open comments.

[adamrtalbot]

Almost there! Some clarification around definitions and what counts against what.