Add WP_CLI_ALIAS_GROUPS_PARALLEL environment variable for concurrent alias group execution

[Copilot]

Add support for parallel processing of alias groups in WP-CLI.

Currently, when running a command against an alias group (e.g., @all or a custom group like @both), WP-CLI processes each alias sequentially. This change adds support for parallel execution via the WP_CLI_ALIAS_GROUPS_PARALLEL environment variable, significantly improving execution speed when running commands across multiple WordPress installations.

Changes Made

• Add WP_CLI_ALIAS_GROUPS_PARALLEL environment variable support
• Modify the run_alias_group() method in Runner.php to check the environment variable
• Add feature tests to validate parallel execution works correctly
• Add documentation and examples for the environment variable
• Ensure backward compatibility (default behavior remains sequential)
• Pass code review with no issues
• Pass security scan with no vulnerabilities
• Fix Gherkin test style to use 'And' instead of 'When'

Implementation Details

The implementation uses the WP_CLI_ALIAS_GROUPS_PARALLEL environment variable:

1. When set to a truthy value (e.g., 1), spawns all alias processes concurrently before waiting for results
2. When not set (default), maintains the original sequential behavior
3. Works with all types of aliases (local paths, SSH, docker, etc.)
4. Environment variable is naturally inherited by child processes

Usage Examples

# Run command against multiple aliases in parallel
WP_CLI_ALIAS_GROUPS_PARALLEL=1 wp @both option get home

# Run command against all registered aliases in parallel
WP_CLI_ALIAS_GROUPS_PARALLEL=1 wp @all plugin list

# Works with quiet mode
WP_CLI_ALIAS_GROUPS_PARALLEL=1 wp @all core version --quiet

Performance Benefits

This change provides significant performance improvements when:

• Running commands across multiple remote installations over SSH
• Executing I/O-bound operations
• Processing commands that take significant time to complete
• Working with installations on different machines or containers

Backward Compatibility

The default behavior remains unchanged - aliases are processed sequentially unless the WP_CLI_ALIAS_GROUPS_PARALLEL environment variable is set. This ensures no breaking changes for existing workflows.

Security Summary

✅ All shell arguments are properly escaped using escapeshellarg()
✅ No new security vulnerabilities introduced
✅ Code review completed with no issues
✅ CodeQL security scan completed with no findings

• Fixes Add switch to allow aliases to be processed in parallel #6128

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add switch to allow aliases to be processed in parallel</issue_title>
<issue_description>It would be useful to allow aliases to be processed in parallel, so that the machine controlling the process can open multiple connections at the same time. Under the right circumstances, this would drastically improve the speed of execution across multiple machines.

From @lukasleitsch via https://twitter.com/lukasleitsch/status/955749917544329216
</issue_description>

Comments on the Issue (you are @copilot in this section)

@danielbachhuber That'd be pretty nifty. It'd even improve performance running across multiple installs on the same machine.

• Fixes Add switch to allow aliases to be processed in parallel #6128

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!