Refactor production blocks registration 1

[monsieur-z]

• See Blocks: use a single source of truth for blocks metadata #32602
• See Blocks: Switch all Production blocks to be registered via their block.json file #33174

Proposed changes:

Registers the following production blocks by specifying the path to their block.json file: AI Assistant, Blogging Prompt, Calendly, Contact Info, Cookie Consent.

This was made possible by #32697. The goal is to avoid the duplication of block metadata and use block.json as the source of truth.

In more details, for each block (when needed):

• Write reading direction-agnostic CSS
• Remove the editorScript property from block.json (automatically added during the build)
• Convert icon from dashicon to SVG in the icon property of block.json
• Remove icon.js
• Import icon helpers from the shared-extension-utils package
• Register the block client and server sides with block.json
• Move data from index.js to block.json and editor.js and delete the file
• Move data from attributes.js to block.json and delete the file
• Fix JS tests

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

pedMtX-RS-p2

Does this pull request change what data or activity we track or use?

No.

Testing instructions:

• Spin up a test site
• Create a new post and open the block inserter
• Test that the aforementioned blocks behave as in trunk. This PR shouldn't change anything from a user's standpoint.

Note: I haven't been able to test the Cookie Consent block.

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WordPress.com Simple site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin, and enable the refactor/production-blocks-registration-1 branch.

• To test on Simple, run the following command on your sandbox:

  bin/jetpack-downloader test jetpack refactor/production-blocks-registration-1
  

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Once your PR is ready for review, check one last time that all required checks appearing at the bottom of this PR are passing or skipped.
Then, add the "[Status] Needs Team Review" label and ask someone from your team review the code. Once reviewed, it can then be merged.
If you need an extra review from someone familiar with the codebase, you can update the labels from "[Status] Needs Team Review" to "[Status] Needs Review", and in that case Jetpack Approvers will do a final review of your PR.

---

Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

• WordPress.com Simple releases happen daily.
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly. The next release is scheduled for November 7, 2023 (scheduled code freeze on October 30, 2023).

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[andrii-lysenko]

Not the biggest concern, but I find it a bit sensitive, as it is possible that at some point we will have a block that will be renamed, or the folder and we might have a mismatch

[monsieur-z]

Having a matching folder name is already a requisite, I believe. We could make sure to document it and add a check in the build process if we feel that's a concern.

[andrii-lysenko]

The code looks good and tests well locally.

I have a small nitpick, but it's not mandatory so you could decide wether change it or not.

The only thing - is that one test from PHP tests: PHP 8.2 WP trunk is failing. Is it a concern?

[monsieur-z]

Thanks @andrii-lysenko! I commented inline.

[The only thing - is that one test from PHP tests: PHP 8.2 WP trunk is failing. Is it a concern?

No, tests for that version of PHP have been flaky lately (I believe this is due to some WordPress updates) and are not currently required. I'll check again after the rebase just to be sure, though.

[jeherve]

I'm noticing an issue with style previews for the Calendly block: both styles look the same with this branch:

[jeherve]

This tests well. I think this is ready to merge! 🥳

I only have one remark, but I do not think it is blocker; it could be fixed in a follow-up PR.

It looks like we're missing chocolate chips on our cookie:

Production

This PR