[Product Block Editor]: do not use sub registry for the IFrame editor

[retrofox]

Submission Review Guidelines:

• I have followed the WooCommerce Contributing Guidelines and the WordPress Coding Standards.
• I have checked to ensure there aren't other open Pull Requests for the same update/change.
• I have reviewed my code for security best practices.
• Following the above guidelines will result in quick merges and clear and detailed feedback when appropriate.

Changes proposed in this Pull Request:

This PR sets the useSubRegistry to false to avoid using a sub-registry in the <BlockEditorProvider> instance of the IFrame editor, keeping in mind that both editor instances cannot coexist simultaneously. The goal is to be able to access to the data globally though the select helpers.

Closes # .

How to test the changes in this Pull Request:

Using the WooCommerce Testing Instructions Guide, include your detailed testing instructions:

To access the Product Editor, follow these steps:

1. Open the dev console
2. Go to the Product Editor

3. From the store, select the current block instances of the editor

wp.data.select( 'core/block-editor').getBlocks()

4. Confirm that the block instances are returned.

To edit the description field using the Modal editor (IFrame editor wrapper), do the following:

5. Open the Modal editor.

6. Choose the block instances.

wp.data.select( 'core/block-editor').getBlocks()

7. Make sure that the instances you see correspond to the Modal editor and not to the Product editor.

8. Close the Modal editor
9. Confirm the app continues working as expected

Changelog entry

• Automatically create a changelog entry from the details below.

Significance

• Patch
• Minor
• Major

Type

• Fix - Fixes an existing bug
• Add - Adds functionality
• Update - Update existing functionality
• Dev - Development related task
• Tweak - A minor adjustment to the codebase
• Performance - Address performance issues
• Enhancement - Improvement to existing functionality

Message

Comment

[github-actions]

Hi , @woocommerce/mothra

Apart from reviewing the code changes, please make sure to review the testing instructions as well.

You can follow this guide to find out what good testing instructions should look like:
https://github.com/woocommerce/woocommerce/wiki/Writing-high-quality-testing-instructions

[github-actions]

Test Results Summary

Commit SHA: 1619f5c

Test 🧪	Passed ✅	Failed 🚨	Broken 🚧	Skipped ⏭️	Unknown ❔	Total 📊	Duration ⏱️
API Tests	259	0	0	2	0	261	0m 37s
E2E Tests	258	0	0	3	0	261	14m 9s

---

To view the full API test report, click here.
To view the full E2E test report, click here.
To view all test reports, visit the WooCommerce Test Reports Dashboard.

[retrofox]

Closing because of #42761 (comment)