New inserter search input-field classname breaks e2e/performance tests

[strarsis]

Describe the bug
The new classname of the search input-field of the inserter breaks the e2e/performance tests because the classname wasn't changed in the test utility functions yet.

Old class name: block-editor-inserter__search-input
New class name: block-editor-inserter__search

To reproduce
Steps to reproduce the behavior:

1. Run the performance test script test-performance (after having prepared everything, also see test-performance build script: Add build:packages/wp-env start scripts as dependency #22038)
2. Notice that the test will fail because of failing to focus on the element -block-editor-inserter__search-input.
3. When you dump the DOM right before the line await page.focus( '.block-editor-inserter__search-input' ); in packages/e2e-test-utils/src/search-for-block.js:14 you will notice that the inserter search input field got the classname block-editor-inserter__search, but the e2e test utility expects the old classname block-editor-inserter__search-input, hence focusing it times out in puppeteer and the test fails.

Expected behavior
e2e/performance tests can finish without errors.

[talldan]

The performance tests in master passed ok for me.

The classname block-editor-inserter__search-input does still seem to be in use:

gutenberg/packages/block-editor/src/components/inserter/search-form.js

Line 25 in 3b5bfa3

className="block-editor-inserter__search-input"

But maybe it was fixed in another ticket. I'll close this given I'm unable to reproduce the issue.

[strarsis]

@talldan: Probably another build task has to be run before the e2e tests and some built files are checked in, that had been built before that commit.