Setup wp-env for E2E tests

[mikkamp]

Changes proposed in this Pull Request:

Our main goal is to convert E2E tests from Puppeteer to PlayWright, as well as remove any dependencies for the WooCommerce E2E packages (as they will be deprecated).

This PR is intended to setup a wp-env site for running the E2E tests against, which previously was done using a docker image as part of @woocommerce/e2e-environment package. A followup PR will address converting tests to PlayWright.

Resolves part of #1599

Detailed test instructions:

1. Checkout this PR and run nvm use && npm ci
2. Start the wp-env site npm run wp-env start
3. Once completed confirm the site is running at http://localhost:8889
4. Run the E2E tests npm run test:e2e and confirm it uses the site http://localhost:8889
5. Expect only some of the tests to pass (some will still fail but that will be fixed when converting to PlayWright)

Additional details:

Some of the tests still fail, because the related products section has switched to blocks and also because some of the tests have been flaking. Since this is the reason we are switching to PlayWright, the failing tests will be addressed there.

It's still possible to get the previous test site up and running with npm run docker:up, all that will be removed once the full dependency on the WooCommerce packages is no longer needed. This is still being used by GitHub actions on release branches.

The command to add a ready page was added because the wc-e2e script waits explicitly till this page is available. Once we convert to PlayWright it should be possible to remove this.

Changelog entry

• Dev - Setup wp-env for E2E tests.

[martynmjones]

Hey @mikkamp,

The environment was properly set up when testing locally and the test:e2e script is using the correct URL so LGTM ✅