Update view config for DataViews/DataForm in the server

[ntsekouras]

This is a continuation of https://core.trac.wordpress.org/ticket/65516 and will port the changes in view config from:

• Add a better default for post types form in view config. GB PR: ​https://github.com/WordPress/gutenberg/pull/79625
• Add pattern (wp_block) form config. GB PR: ​https://github.com/WordPress/gutenberg/pull/79452

## What?
This is a follow-up to WordPress/wordpress-develop#11272 and will port the changes in view config from:

• Add a better default for post types form in view config. GB PR: ​https://github.com/WordPress/gutenberg/pull/79625
• Add pattern (wp_block) form config. GB PR: ​https://github.com/WordPress/gutenberg/pull/79452

## Testing
Verify unit tests are passing.

I suggest opening a new ticket linking back to the original one.

I opened a new trac ticket for this PR which will include two PRs from GB (see description)

[ntsekouras]

In 62588:

Add default post type and pattern forms to view config.

Apply a single default form to every post type in wp_get_entity_view_config() instead of registering an identical form per type, so post, page, and custom post types all receive a sensible default. Post types that need a different shape can still replace it entirely through their own get_entity_view_config_postType_{$post_type} filter callback. The default is intentionally not gated by supports: the registered fields are the single source of truth, and the editor drops any field whose definition is absent or whose isVisible returns false.

Add a dedicated form for the wp_block (pattern) post type, covering excerpt, content info, sync status, and revisions.

This ports the changes from the Gutenberg plugin. See ​https://github.com/WordPress/gutenberg/pull/79625 and ​https://github.com/WordPress/gutenberg/pull/79452.

Follow-up to [62547].

Props jorgefilipecosta, ntsekouras, mcsf.
Fixes #65552.