Description

In #27303, the behavior of template resolution was changed such that a custom manually-created user template no longer overrides a theme template which has the same slug. This breaks the test because the test assumes two things:

1. That the site editor will load the template used for the front page by default.
2. That a custom manually created template with the slug front-page will always be used instead of the theme template with the same slug.

These assumptions should not be taken by the test, so we need to make it more robust. The failure always seems unrelated since these PRs continue to be merged. :P This PR fixes the issue by using a user created custom template which doesn't correspond to the template hierarchy. This way, it's not possible for a theme file to conflict with it. This test is only concerned with making sure that entity save states work correctly, so this is a fine approach for this test.

We should also follow up to create tests which cover the template resolution hierarchy so that it is more obvious when we are breaking it in some way or another. Currently I don't think we cover template priorities at all with tests. We definitely shouldn't rely on some unrelated test to inform us when it is broken :P

How has this been tested?

The multi entity editing test should pass. (I verified it does locally.)

Screenshots

Types of changes

Fix

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• My code has proper inline documentation.
• I've included developer documentation if appropriate.
• I've updated all React Native files affected by any refactorings/renamings in this PR.