wp-env: Add --skip-confirmation option to destroy command

[jrmd]

What?

This patch adds support for wp-env destroy --skip-confirmation which allows for the command to be ran without the blocking confirmation prompt.

Why?

I am currently creating a script to run e2e tests across numerous plugins/repos all with their own individual e2e tests set up that need to be ran independently, when trying to run wp-env destroy within the script it requires a confirmation from stdin, forcing me to to write to stdin in a rather clunky way. By adding the skip confirmation option allows us to bypass this limitation allows the script to cleanup without issue.

How?

PR adds an optional argument to the destroy command which is used to skip over the confirmation prompt to assume yes.

Testing Instructions

1. run wp-env destroy --skip-confirmation
2. see the confirmation isn't shown and the environment is destroyed as expected
3. run wp-env destroy
4. see the confirmation prompt is shown and works as previous

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: jrmd <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @jrmd! In case you missed it, we'd love to have you join us in our Slack community.

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