Update permalink structure using Playwright global setup

[MrJnrman]

All Submissions:

• Have you followed the WooCommerce Contributing guideline?
• Does your code follow the WordPress' coding standards?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes proposed in this Pull Request:

This PR addresses a limitation with wp-env that didn't allow us to properly update permalink settings to the format that the E2E tests expected.

Reference: WordPress/gutenberg#28201

The work done here is to use PW to update the permalinks using the global-setup.js file in much the same way it adds the consumer tokens for admin and customer users.

How to test the changes in this Pull Request:

1. Checkout this branch
2. Specify the WordPress version in the plugins/woocommerce/.wp-env.json file. (e.g. "core": "WordPress/WordPress#tags/5.8.6")
3. Run test using pnpm env:test --filter=woocommerce && USE_WP_ENV=1 npx playwright test --config=tests/e2e-pw/playwright.config.js
4. Confirm that the tests are successfully executed.

Note: WooCommerce currently has a minimum WP version of 5.8.

Other information:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes, as applicable?
• Have you created a changelog file for each project being changed, ie pnpm changelog add --filter=<project>?

FOR PR REVIEWER ONLY:

• I have reviewed that everything is sanitized/escaped appropriately for any SQL or XSS injection possibilities. I made sure Linting is not ignored or disabled.

[github-actions]

Test Results Summary

Commit SHA: 61f7abb

Test 🧪	Passed ✅	Failed 🚨	Broken 🚧	Skipped ⏭️	Unknown ❔	Total 📊	Duration ⏱️
API Tests	203	0	0	2	0	205	0m 43s
E2E Tests	186	0	0	6	0	192	14m 38s

---

To view the full API test report, click here.
To view the full E2E test report, click here.
To view all test reports, visit the WooCommerce Test Reports Dashboard.

[lanej0]

Solid change, thanks for this @MrJnrman.

[github-actions]

Hi @lanej0, thanks for merging this pull request. Please take a look at these follow-up tasks you may need to perform:

• Add the release: add testing instructions label