Improve argument alias parsing and --prompt support

[swissspidy]

This is a follow-up to #6176

I noticed this bug in wp-cli/core-command#335

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[Copilot]

Pull request overview

This PR is a follow-up to argument-alias support (#6176) that fixes alias parsing for assoc args when the =<value> spec is attached to an alias instead of the canonical name, and extends --prompt so it can target parameters via either their canonical name or any alias.

Changes:

• Update SynopsisParser::classify_token() to extract assoc value specs before splitting out pipe-based aliases, so --canonical|alias=<value> is parsed correctly as an assoc parameter.
• Extend Subcommand::prompt_args() matching so --prompt= can reference assoc parameters by alias name as well as canonical name.
• Add feature scenarios covering prompting with aliases and bypassing prompts when an alias is supplied on the command line.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
php/WP_CLI/SynopsisParser.php	Fixes parsing order so assoc value specs are recognized even when written on an alias segment.
php/WP_CLI/Dispatcher/Subcommand.php	Allows --prompt to match assoc args via aliases, aligning prompting behavior with alias resolution.
features/arg-aliases.feature	Adds coverage for --prompt + aliases, including value-spec-on-alias cases and prompt bypass.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.