Call for testing: DataForm editor inspector

Part of Consolidate QuickEdit and Editor Inspector issue: https://github.com/WordPress/gutenberg/issues/76076

There is also a make/core post with suggested testing flows and Playground links.

A small call for testing for plugin developers, since this affects anything that extends the editor's post inspector(the "Post" or "Page" tab of the Settings sidebar).

With the "Editor Inspector: Use DataForm" experiment enabled (Settings > Gutenberg), the classic summary panels (featured image, excerpt, status, date, author, template, etc..) are replaced by the same DataForm that Quick Edit uses in the Site Editor, for every post type that uses the block editor. There are tests and manual testing for the core post types and simple CPTs, but a pass with other user roles would be helpful and might catch something. What I'd love help with most though is what plugins add on top.

If your plugin extends the post inspector in any way (filters, slots, panels, styles, scripts) or registers custom post types that use the block editor, could you give it a pass with Gutenberg 24.0 or newer and the experiment on, and compare with the experiment off? Whatever you add or change there, is it still there and does it still work? Trunk has a few more fixes than 24.0, so if you can run it, even better (it needs WordPress 7.0 or later).

What to expect:

• PluginDocumentSettingPanel, PluginPrePublishPanel, PluginPostPublishPanel, PluginSidebar, PluginPostStatusInfo fills and removeEditorPanel keep working.
• The PluginPostExcerpt slot is not ported and since it's a deprecated API we're considering not adding it at all. Whatever you render there should move to a PluginDocumentSettingPanel.
• The editor.PostFeaturedImage filter doesn't work yet. There is a PR which adds it, though not in Quick Edit. Anything targeting the classic panels' CSS class names or markup won't be ported. If you use that filter, testing with the PR applied would help too, this Playground link has it with the experiment on.
• The featured image picker doesn't go through the editor.MediaUpload filter yet. This PR adds that but is on hold (see here). If you use that filter, testing with the PR applied would help too, this Playground link has it with the experiment on.

The end goal is the fields API, where you register your own fields and they show up in the inspector and in Quick Edit (#61084, #74865). It's aimed for 7.2.

Until then, anything you need in the inspector can go in a PluginDocumentSettingPanel. Hiding a core row or changing where its label sits is already possible with the server side view config filter, get_entity_view_config_posttype_post for posts (see docs). For example, this hides the Format row and moves the Author label above its field:

add_filter( 'get_entity_view_config_posttype_post', function ( $data ) {
      $data->remove( array( 'form' => array( 'fields' => array( 'format' ) ) ), 1 );
      $data->merge(
              array(
                      'form' => array(
                              'fields' => array(
                                      array(
                                              'id'     => 'author',
                                              'layout' => array( 'type' => 'panel', 'labelPosition' => 'top' ),
                                      ),
                              ),
                      ),
              ),
              1
      );
      return $data;
} );

Please comment here with what you extend, what changed and whether you can adapt on your side or need something from Gutenberg. "Checked X, nothing changed" is useful too. If you're reporting as a user of a plugin, the plugin name and version and a screenshot with the experiment on and off are enough. Thanks!