Description

This PR explicitly closes the Inserter after a block is successfully installed from the Block Directory.

Ideally, we would want the default inserter behaviour to determine whether the inserter should close or not. At the moment of this PR, the inserter closes when a block is added.

However, it appears like the async calls that are triggered when a user clicks "Install" on a block directory block do not trigger the same code paths/timings as regular blocks.

In order to solve #24606, there appear to be 2 choices:

1. Modify popover-wrapper.js & with-focus-outside
   • There is logic that is preventing the triggering of the onClose function that closes the inserter.
2. Explicitly close the inserter in the block directory package. (implemented here)

How has this been tested?

1. Search for "p5"
2. Click to install the block
3. Notice the block is inserted and the inserter closes.

Drawbacks

As mentioned above if the main inserter goes back to not closing on block add, this will fall out of sync.

Types of changes

• When the block is inserted successfully, trigger setIsInserterOpened and close the inserter

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.