Always run initialization code before Playwright e2e tests

[kevin940726]

What?

Discovered in #46452 by @t-hamano. The requestUtils fixture is not initialized if the test doesn't use it.

Why?

We need to run some initialization steps before any e2e tests (switching themes for instance), hence the requestUtils fixture needs to be initialize even when it's not used in tests.

How?

Add { auto: true } to the fixture options.

Testing Instructions

1. Publish a random post in the test WP instance.
2. On trunk, run the buttons tests only via npm run test:e2e:playwright -- buttons (it doesn't use requestUtils)
3. The post should still be there.
4. Apply this PR, and repeat the same. After the tests, the post should be deleted.

[t-hamano]

Thanks for the fix!

Publish a random post in the test WP instance.
On trunk, run the buttons tests only via npm run test:e2e:playwright -- buttons (it doesn't use requestUtils)
The post should still be there.
Apply this PR, and repeat the same. After the tests, the post should be deleted.

I have confirmed that the above steps returns the expected result.
At the same time, I also confirmed that Twenty Twenty One is automatically activated when the test is run.

I noticed that some test files have the following processing. Should these codes be removed?

test.afterEach( async ( { requestUtils } ) => {
	await requestUtils.deleteAllPosts();
} );

[alexstine]

LGTM.

[kevin940726]

I noticed that some test files have the following processing. Should these codes be removed?

I don't think so. Those are run after each test while the fixture will only run once before running the test suite.