Testing: Remove e2e-test-utils package and deprecated test configuration (#72880)

* Testing: Remove e2e-test-utils package and deprecated test configuration

* Remove unused dependency from e2e-test-utils-playwright

* Remove lockfile reference to e2e-test-utils

Co-authored-by: aduth <[email protected]>
Co-authored-by: manzoorwanijk <[email protected]>
Co-authored-by: Mamaduka <[email protected]>

Author: 3 people

.github/CODEOWNERS

@@ -66,7 +66,6 @@
 /packages/create-block-tutorial-template        @ryanwelcher
 /packages/dependency-extraction-webpack-plugin
 /packages/docgen
-/packages/e2e-test-utils                        @ntwb @nerrad @ajitbohra
 /packages/e2e-tests                             @ntwb @nerrad @ajitbohra
 /packages/e2e-test-utils-playwright             @kevin940726
 /packages/eslint-plugin                         @ntwb @nerrad @ajitbohra

docs/contributors/code/e2e/README.md

@@ -2,12 +2,6 @@
 
 This living document serves to prescribe instructions and best practices for writing end-to-end (E2E) tests with Playwright in the Gutenberg project.
 
-<div class="callout callout-info">
-
-See the dedicated guide if you're working with the previous Jest + Puppeteer framework. See the <a href="https://github.com/WordPress/gutenberg/tree/HEAD/docs/contributors/code/e2e/migration.md">migration guide</a> if you're migrating tests from Jest + Puppeteer.
-</div>
-
-
 ## Running tests
 
 ```bash
@@ -69,9 +63,9 @@ See the [official documentation](https://playwright.dev/docs/locators) for more
 
 To encourage better practices for querying elements, selectors are [strict](https://playwright.dev/docs/api/class-browser#browser-new-page-option-strict-selectors) by default, meaning that it will throw an error if the query returns more than one element.
 
-### Don't overload test-utils, inline simple utils
+### Inline simple utility helper function
 
-`e2e-test-utils` are too bloated with too many utils. Most of them are simple enough to be inlined directly in tests. With the help of accessible selectors, simple utils are easier to write now. For utils that only take place on a certain page, use Page Object Model instead (with an exception of clearing states with `requestUtils` which are better placed in `e2e-test-utils`). Otherwise, only create an util if the action is complex and repetitive enough.
+Most utility functions are simple enough to be inlined directly in tests. With the help of accessible selectors, simple utils are easier to write now. For utils that only take place on a certain page, use Page Object Model instead. Otherwise, only create an util if the action is complex and repetitive enough.
 
 ### Favor Page Object Model over utils
 

docs/contributors/code/e2e/migration.md

@@ -1649,12 +1649,6 @@
 		"markdown_source": "../packages/e2e-test-utils-playwright/README.md",
 		"parent": "packages"
 	},
-	{
-		"title": "@wordpress/e2e-test-utils",
-		"slug": "packages-e2e-test-utils",
-		"markdown_source": "../packages/e2e-test-utils/README.md",
-		"parent": "packages"
-	},
 	{
 		"title": "@wordpress/e2e-tests",
 		"slug": "packages-e2e-tests",
@@ -2309,12 +2303,6 @@
 		"markdown_source": "../docs/contributors/code/e2e/README.md",
 		"parent": "testing-overview"
 	},
-	{
-		"title": "Migration guide",
-		"slug": "migration",
-		"markdown_source": "../docs/contributors/code/e2e/migration.md",
-		"parent": "e2e"
-	},
 	{
 		"title": "Overusing snapshots",
 		"slug": "overusing-snapshots",

docs/manifest.json

@@ -373,9 +373,6 @@
 						"docs/contributors/code/testing-overview.md": [
 							{
 								"docs/contributors/code/e2e/README.md": [
-									{
-										"docs/contributors/code/e2e/migration.md": []
-									},
 									{
 										"docs/contributors/code/e2e/overusing-snapshots.md": []
 									}

docs/toc.json

@@ -39,7 +39,6 @@
 	"types": "./build-types",
 	"dependencies": {
 		"change-case": "^4.1.2",
-		"form-data": "^4.0.0",
 		"get-port": "^5.1.1",
 		"lighthouse": "^12.2.2",
 		"mime": "^3.0.0",