Backport: move new wp_block postmeta field to a top level field of wp_block in rest responses and rename to wp_pattern_sync_status

[glendaviesnz]

As [discussed here](​https://github.com/WordPress/wordpress-develop/pull/4646#issuecomment-1603668189) this moves the sync_status postmeta to a top level field of wp_block, and also renames it to wp_pattern_sync_status as [discussed here](​https://wordpress.slack.com/archives/C02QB2JS7/p1688091498250399).

The rename to wp_sync_status is not 100% confirmed yet, we can back that out if needed.

[Related GB PR.](​https://github.com/WordPress/gutenberg/pull/52146)

As ​discussed here this moves the sync_status postmeta to a top level field of wp_block, and also renames it to wp_sync_status as ​discussed here.

The rename to wp_sync_status is not 100% confirmed yet, we can back that out if needed.

​Related GB PR.

Trac ticket: [](https://core.trac.wordpress.org/ticket/58677)

@TimothyBJacobs is this the sort of thing you were thinking ​in this comment?

This will need to be merged alongside the next lot of editor updates to be pulled in as it is dependent on those.

It would be good to have a test for the postmeta field being moved up to top level field in rest response - will try and get that added tomorrow.

@aaronrobertshaw I have ​added that unit test. The e2e failures seem unrelated but I do not have the option to restart them.

Just to confirm that this PR also covers the changes in:

• ​https://github.com/WordPress/gutenberg/pull/52232

Unfortunately, I do not have that ability either. Perhaps @tellthemachines or @ramonjd could help here?

I too am not a member of the exalted group 😄

Just to confirm that this PR also covers the changes in:

• ​Patterns: rename sync_status postmeta to pattern_post_sync_status gutenberg#52232

except for ​this bit which is only needed in plugin, not core.

I restarted the tests. They've been super flaky lately so failures are unlikely to be related to this PR.

Committed in r56160 / ​7035b61.

[swissspidy]

@isabel_brison FYI you forgot the "#" when referencing the ticket number in your commit message.

Manually marking this as fixed now.

[swissspidy]

Though I actually have to say that "6.3" should really be "6.3.0" in that @since annotation.

But then again, AFAIK we don't typically add @since annotations for new fields being added.

I recommend checking with #core-restapi

[isabel_brison]

Thanks @swissspidy ! I'll ask about it in #core-restapi.

[kebbet]

Reopening for visibility, regardning the @since tag.

Trac ticket: https://core.trac.wordpress.org/ticket/58677

[isabel_brison]

In 56217:

Editor: fix since annotation in rest blocks controller class.

Changes 6.3 to 6.3.0 in the since annotation for the filter_response_by_context function.

Props swissspidy, peterwilsoncc, mukesh27.
Fixes #58677.

Committed in r56217 / ​ee7434f.