fix: update block category to design and build documentation.

[snehapatil2001]

Issue: #60930

Description

Issue

The experimental Table of Contents block in the Gutenberg repository is using the category "layout" in its block.json file. However, "layout" is not listed as a valid block category according to the block.json schema. The valid categories are:

• "text"
• "media"
• "design"
• "widgets"
• "theme"
• "embed"

Solution

This PR resolves the issue by changing the category of the Table of Contents block from "layout" to "design", which is one of the valid categories listed in the schema. This ensures that the block complies with the schema and avoids any validation issues.

Changes

• Updated the block.json file for the experimental Table of Contents block to change the category from "layout" to "design".
• Build Documentation.

Tests

• Verified that the block appears correctly under the "design" category in the block inserter.
• Checked that the block functions as expected without any validation errors.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: snehapatil2001 <snehapatil02@git.wordpress.org>
Co-authored-by: fabiankaegy <fabiankaegy@git.wordpress.org>
Co-authored-by: akasunil <sunil25393@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @snehapatil2001! In case you missed it, we'd love to have you join us in our Slack community.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.

[fabiankaegy]

Great catch. Thanks for the fix :)

[snehapatil2001]

@fabiankaegy Do I have to make any more changes or is it good to be merged??

[akasunil]

@snehapatil2001 Yes, it ready for merge once all checks are passed. I see some tests are still pending, Can you sync with trunk? that might resolve it.

[snehapatil2001]

@akasunil Synced up with trunk.

[t-hamano]

Hi @akasunil,

When you merge the pull request, please paste the props mentioned in this comment into the commit message.