Plugin Directory: Hide ElasticSearch metabox where unusable + populate post_author for CLI inserts

[dd32]

Two small fixes around the wp-admin plugin edit screen, motivated by PHP warnings showing up when running locally:

Hide the ElasticSearch metabox when it cannot be useful

• For plugins in draft or pending status there is nothing indexed yet, so the metabox just shows "Not indexed" with a Reindex button that will not help.
• On non-production/staging environments without Jetpack Search available locally, the AJAX call cannot reach the index at all.

The metabox now registers only when neither of those conditions apply.

Local env mu-plugin: populate post_author for CLI inserts

The production import-plugin.php --create path calls Plugin_Directory::create_plugin_post() with only post_name, so wp_insert_post() defaults post_author to get_current_user_id() — which is 0 in CLI. Locally-imported plugin posts end up with no resolvable author, which then produces a wall of PHP warnings in the Review Tools metabox ($author->user_email, ->user_registered, etc on false).

The new environments/mocks/mu-plugins/wporg-plugin-author-import.php hooks wp_insert_post_data (CLI-only, new inserts, missing post_author) and resolves the author from https://wordpress.org/plugins/wp-json/wp/v2/plugin?slug=...&_embed=1, creating a matching local user if needed.

Test plan

• In wp-admin on a draft plugin, the ElasticSearch metabox is hidden.
• On a local env without Jetpack Search available, the ElasticSearch metabox is hidden for any plugin.
• In a production-mode local env (or one with Jetpack Search active), the metabox still appears for published plugins.
• Running wp eval-file wp-content/plugin-directory/bin/import-plugin.php --plugin=<slug> --create against a fresh local DB results in the plugin post being created with post_author set to the matching wp.org user (auto-created locally).
• The Review Tools metabox for that plugin opens without PHP warnings.

🤖 Generated with Claude Code

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

Core Committers: Use this line as a base for the props when committing in SVN:

Props dd32.

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