Add network tags support for Google Batch

[ejseqera]

This PR implements the feature request from #5950 to add support for configuring network tags when running Nextflow pipelines on Google Batch. Network tags can be specified in the Nextflow config file and will be applied to the Batch job's allocation policy.

Changes:

• Added networkTags property to BatchConfig
• Updated GoogleBatchTaskHandler to apply tags to the AllocationPolicy
• Added warning when tags are specified with instance templates

Example config:

google {
    batch {
        networkTags = ['nextflow-test']
    }
}

[netlify]

✅ Deploy Preview for nextflow-docs-staging ready!

Name	Link
🔨 Latest commit	a7fef21
🔍 Latest deploy log	https://app.netlify.com/sites/nextflow-docs-staging/deploys/6807e8b09143c700080a1a3c
😎 Deploy Preview	https://deploy-preview-5951--nextflow-docs-staging.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 site configuration.

[ejseqera]

Tested with a simple hello world run:

[pditommaso]

Would not resourceLabels cover this use case? As a user when I should use networkTags instead of resourceLabels?

nextflow/plugins/nf-google/src/main/nextflow/cloud/google/batch/GoogleBatchTaskHandler.groovy

Line 294 in 5204d27

allocationPolicy.putAllLabels( task.config.getResourceLabels() )

[ejseqera]

@pditommaso No, they're different things. Network tags are used to apply firewall rules and control network traffic to your instances. Resource labels cannot be used for network security controls and are key-value pairs used for just resource organization (e.g. cost tracking).

They're also structured differently in the API: tags are a simple list of strings at the root of the AllocationPolicy (tags: [string]), while labels are key-value pairs (labels: {string: string}).

[pditommaso]

Fair enough. @bentsherman is there not a new annotation for config settings?

[bentsherman]

• update "maximal spec" test in GoogleBatchTaskHandlerTest
• add config option to docs reference/config.md
• add config option to schema GoogleBatchConfig.java (use the same description from the docs)

[christopher-hakkaart]

Minor language suggestions. Please check meaning is retained.

[bentsherman]

The only remaining issue is the DCO signoff. @ejseqera if you click on the failing check it will take you to instructions for how to fix the DCO. I think you will have to rebase the branch. Don't worry about overwriting our commits if you need to