test: Mobile editor mocks getPostType resolution

[dcalhoun]

What?

Fix failing mobile editor unit tests.

Why?

The erroneous test failures are misleading.

How?

The mobile editor only supports the post-only rendering mode, so we presume a resolved getPostType selector to unblock editor rendering. This is necessary as the editor provider awaits post type resolution before rendering the entirety of the editor.

Testing Instructions

N/A, no user-facing changes.

Testing Instructions for Keyboard

N/A, no user-facing changes.

Screenshots or screencast

N/A, no user-facing changes.

[dcalhoun]

@fabiankaegy this is ready for review and merge. It should fix the failing mobile editor automated tests.

[github-actions]

Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Type-related labels to choose from: [Type] Automated Testing, [Type] Breaking Change, [Type] Bug, [Type] Build Tooling, [Type] Code Quality, [Type] Copy, [Type] Developer Documentation, [Type] Enhancement, [Type] Experimental, [Type] Feature, [Type] New API, [Type] Task, [Type] Technical Prototype, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core, Gutenberg Plugin.
• Labels found: .

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

[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: dcalhoun <[email protected]>

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

[fabiankaegy]

The code here look good to me :)

And I ran the tests locally and can confirm they are also fixed for me there 🎉