Update Performance tests base branch

[ramonjd]

What? Why? How?

One option to fix failing tests.

Alternative here: #59266

Updates performance tests base branch after #59259

See: #59259 (comment)

Testing Instructions

CI checks should pass.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: ramonjd <ramonopoly@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

Flaky tests detected in 35c8b1e.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/8000263835
📝 Reported issues:

• [Flaky Test] can add submenus #50976 in /test/e2e/specs/editor/blocks/navigation-list-view.spec.js
• [Flaky Test] can edit menu items #59006 in /test/e2e/specs/editor/blocks/navigation-list-view.spec.js
• [Flaky Test] default to the only existing classic menu if there are no block menus #48033 in /test/e2e/specs/editor/blocks/navigation.spec.js

[ramonjd]

Closing in favour of #59266