Description

Partially addresses #27998.

Improvements towards resolving the issue raised in #29938 by @jeremyfelt:

After adding an admin notice, the plugin bails with return; and Gutenberg libraries are not loaded. Other hooks are added by the plugin that require those libraries, and a fatal error occurs rather than a compatibility notice. This removes the return, which helps to eliminate immediate fatal errors and allows the notice to be shown.

A (likely preferable) alternative to item 3 would be to remove all other functionality from the main plugin file so that it too is only loaded when gutenberg_pre_init() fires successfully.

Current culprits appear to be:

modify_welcome_panel()
modify_admin_bar()
gutenberg_site_editor_menu()
gutenberg_menu()

This PR moves the logic that causes issues to their own file that is conditionally loaded through the lib/load.php entry point.

How has this been tested?

Plugin should load as usual.

Types of changes

Refactoring.

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• I've tested my changes with keyboard and screen readers.
• 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.