(3P) Update block categorization in CoBlocks

[obenland]

As a writer, I'd like blocks to be categorized appropriately, so they are easier for me to find.

Acceptance Criteria:

• Blocks make use of four new categories: Blog, Earn, Marketing, and Social.
• Blocks are part of the assigned category.
• Blocks are not within a "collection" category (meaning "Jetpack" or "Coblocks").

Resources:

• Spreadsheet with Blocks and their new categories.

Implementation Notes

• Confirm it's ok to register the same Category twice without causing an error. This is in case Core creates a new Category with the same as ours. (Also can we check for cat exists before creating?).

How to Demo:

• In the block selector, identify two or three blocks that found their new home in a core-registered or custom category.
• Show how blocks not make use of "collection" categories anymore.

More discussion: p58i-8yl-p2.

[obenland]

@lessbloat We was wondering if there's a list of the blocks this should apply to, that ideally would also include the category and collection they should fall into?

[davemart-in]

I outlined my proposal for 4 collections here. Let's hold off on category changes until this core PR is merged.

[obenland]

The issue description was updated and reflects the latest status of this task

[marekhrabe]

Let's make sure newly registered categories (like "Layout") would not cause a fatal error if other plugin or core decides to register the same name.

[retrofox]

Let's make sure newly registered categories (like "Layout") would not cause a fatal error if other plugin or core decides to register the same name.

Adding a new category with the same slug produces a funny visual bug. Basically, both sections in the accordion will act as a single one. it means if you open one of them, both will be open. Same closing the accordion.
Also, both section containers are filled with the same blocks, which makes sense because the category slug is for both sections.

[retrofox]

in #14721 I've handled the categories straight in Jetpack. We agreed that it'd be better to handle them in the respective repositories. For instance, for coblocks we should tackle them at https://github.com/Automattic/coblocks-builder, and so on with other blocks.

[frontdevde]

Let's hold off on category changes until this core PR is merged.

WordPress/gutenberg#19279 still hasn't been merged and it looks like the discussion in core is stalling.

[obenland]

Jetpack side is done, only CoBlocks category update remains