fix rawHandling, pasteHandling for mixed content with blocks and classic

[saulyz]

What?

The rawHandler and the pasteHandler had a naive check for the block existence. The test was looking for string "<!-- /wp:" existence in the content. When mixed content exist, this would give positive result and would try to parse blocks thus wrongfully interpreting and failing.

Why?

When we convert legacy content to blocks sometimes whole article or some parts silently fail. Clicking "convert to blocks" does nothing - everything stays the same. In the Editor view one could not distinguish a problem content and would not get any error.

How?

Not changing the overall logic or the process, instead refining the check further checking if parsing has resulted with the same 'core/freeform' block. If content parsing results with the same and single freeform, let's continue the content conversion (previously process would stop).

Testing Instructions

Adding test files to PR that illustrate the issue.

Testing Instructions for Keyboard

Screenshots or screencast

[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.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @vvdc@vvdcs-MacBook-Pro.local, @saulyz.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

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

Unlinked contributors: vvdc@vvdcs-MacBook-Pro.local, saulyz.

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

[github-actions]

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @saulyz! In case you missed it, we'd love to have you join us in our Slack community.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.

[saulyz]

@ellatrix need your eyes here

[ellatrix]

I'm surprised this was never caught earlier.

[ellatrix]

I just cherry-picked this PR to the wp/6.6-beta-3 branch to get it included in the next release: e08c158