Fix iframe error when accessing patterns on post command palette

[xavier-lc]

Related to #92634

Proposed Changes

• Handle the user's interaction with the Patterns command on the command palette through the iframe bridge, so the destination page can be opened as expected instead of being blocked because of it being inside an iframe.

Why are these changes being made?

• Currently, clicking on the Patterns command on the command leaves the users with an error page and this message on the console: Refused to display 'https://xavilc12.wordpress.com/' in a frame because it set 'X-Frame-Options' to 'sameorigin'.

Testing Instructions

• Checkout this branch locally on the wp-calypso folder
• Go to the apps/wpcom-block-editor folder inside wp-calypso
• Run yarn dev --sync, this will add the necessary changes to your sandbox
• Sandbox widgets.wp.com
• Open the calypso live preview
• Go to /post
• Select a site with the default interface (otherwise, you'll be redirected to wp-admin and won't use the iframe editor)
• Click on the command palette, and then type Patterns and click on it
• Check that you are redirected to the patterns page:

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-117258

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-117258&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-117258&env=a8c-for-agencies

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Sections (~36 bytes added 📈 [gzipped])

name              parsed_size           gzip_size
gutenberg-editor       +149 B  (+0.0%)      +36 B  (+0.0%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• notifications
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug fix/iframe-error-when-accessing-patterns-on-post-command-palette on your sandbox.

[TimBroddin]

Amazing work! 🎈
Works as intended & code checks out!