Env: Fixed run Argument Passing

[ObliviousHarmony]

What?

As it stands, you need to pass options to wp-env run with the entire string having been quoted. This is because of yargs/yargs consuming any options even if they aren't defined. This causes problems when trying to encapsulate scripts in package.json files since you can't easily inject more options into the quoted string in the script.

Closes #32929.

Why?

This will make it easier to write wp-env run commands in package.json scripts that can accept more options. Something like wp-env run tests-wordpress ls -la will now work without being quoted. With this pull request, you can now pass options.

How?

This works by enabling the unknown-options-as-args parser option. This results in any unknown options that are given being treated as a positional argument. In the case of a variadic argument like [command...], this means we can write commands conveniently.

As a note, --help and --version cannot be passed since they are known options. This will also result in other commands failing to execute if unknown flags are passed inappropriately in place of positional arguments.

Testing Instructions

1. Run npm run wp-env -- run ls -la
2. With this pull request the command will execute as expected. Without it, there will be no -la option.3.

[github-actions]

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @ObliviousHarmony! In case you missed it, we'd love to have you join us in our Slack community, where we hold regularly weekly meetings open to anyone to coordinate with each other.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.

[noahtallen]

Love it, very simple way to solve the problem! And quotes still work if the argument matches a wp-env argument as a fallback.

I think we just need to update the README file. For example, we have this notice about needing quotation marks in some cases:

gutenberg/packages/env/README.md

Lines 302 to 312 in c088c44

	<div class="callout callout-alert">
	To run a WP-CLI command that includes optional arguments, enclose the WP-CLI command in quotation marks; otherwise, the optional arguments are ignored. This is because flags are normally passed to `wp-env` itself, meaning that the flags are not considered part of the argument that specifies the WP-CLI command. With quotation marks, `wp-env` considers everything inside quotation marks the WP-CLI command argument.
	For example, to list cron schedules with optional arguments that specify the fields returned and the format of the output:
	```sh
	wp-env run cli "wp cron schedule list --fields=name --format=csv"
	```
	Without the quotation marks, WP-CLI lists the schedule in its default format, ignoring the `fields` and `format` arguments.
	</div>

, so we can probably remove that and note that quotation marks can be used as a fallback if wp-env consumes an arg instead of passing it in.

Edit: oh and we should also note it as an enhancement in the changelog :)

[ObliviousHarmony]

Thanks, @noahtallen,

I've added a changelog and updated the documentation.

[github-actions]

Congratulations on your first merged pull request, @ObliviousHarmony! We'd like to credit you for your contribution in the post announcing the next WordPress release, but we can't find a WordPress.org profile associated with your GitHub account. When you have a moment, visit the following URL and click "link your GitHub account" under "GitHub Username" to link your accounts:

https://profiles.wordpress.org/me/profile/edit/

And if you don't have a WordPress.org account, you can create one on this page:

https://login.wordpress.org/register

Kudos!