Fix WP_Block_Supports class compatibility with Gutenberg-provided class

[oandregal]

The WP_Block_Supports class is a new addition that will come with 5.6 and acts as a register of the kind of features a block supports. It's already on WordPress 5.6 beta1 and we need to fix how core and the plugin play together in a number of situations:

• plugin + WordPress < 5.6 (core has a WP_Block_Supports class)
• plugin + WordPress >= 5.6 (core doesn't have a WP_Block_Supports class)

Related:

• Gutenberg ​https://github.com/WordPress/gutenberg/pull/26356
• Core patch https://core.trac.wordpress.org/ticket/51606#ticket

The WP_Block_Supports class is a new addition that will come with 5.6 and acts as a register of the kind of features a block supports. It's already on WordPress 5.6 beta1 and we need to fix how core and the plugin play together in a number of situations:

plugin + WordPress < 5.6 (core has a WP_Block_Supports class)
plugin + WordPress >= 5.6 (core doesn't have a WP_Block_Supports class)

[oandregal]

There's a Pull Request to fix this at ​https://github.com/WordPress/wordpress-develop/pull/640

[oandregal]

The pull request has been udpated and all tests are passing. This is ready for review/commit.

I won't be able to test this today but it's looking good to me if anyone wants to ship it :)

[youknowriad]

In 49310:

Block Editor: Fix WP_Block_Supports class compatibility with Gutenberg-provided class.

When using WordPress trunk with Gutenberg master, there's an incompatibility causing
the dynamic block generated classes to be omitted.
This commit refactors the block supports to fix that problem.

Props nosolosw.
Fixes #51606.

Thanks for fixing this ❤️

[SergeyBiryukov]

In 49312:

Docs: Correct DocBlock formatting for render_block().

Follow-up to [49310].

See #51606.

Merged with changeset https://core.trac.wordpress.org/changeset/49310 and https://core.trac.wordpress.org/changeset/49312

[SergeyBiryukov]

In 49540:

Coding Standards: Adjust formatting in WP_Block::render() for better readability.

Follow-up to [49310], [49539].

See #51606.