feat: allows having dynamic zones in components

[AtiX]

What does it do?

Allows adding dynamic zones in components, making the overall data model more flexible.

Why is it needed?

This solves a typical use case where strapi is being used as a pagebuilding CMS, closing the gap to other solutions like storyblok.

A typical pagebuilding approach looks like:

1. Have a page data model
2. Have multiple blocks defined as components (such as a HeroBlock, ImageAndText, CtaBlock, ...) which are rendered in the frontend, e.g. as individual react components
3. On the page, have some sort of contentBlocks dynamic zone where those blocks can be placed to build up the page.

Now, the current issue is that those blocks cannot contain dynamic zones themselves. However, for proper pagebuilding, one does need it:

• Imagine a TwoColumnBlock that just implements a two-column layout without having to care about what is contained "in it" (= defined a leftColumn and rightColumn dynamic zone).
• Imagine a CtaBlock that stands out visually, which however may contain other content elements itself
• ...

This PR solves this issue by allowing those dynamic zones in components.

How to test it?

1. You should be able to define dynamic zones in the content type builder inside a component
2. You should then be able to place a component and elements within its dynamic zones.

Related issue(s)/PR(s)

• https://feedback.strapi.io/developer-experience/p/dynamic-zone-in-components

[vercel]

@AtiX is attempting to deploy a commit to the Strapi Team on Vercel.

A member of the Team first needs to authorize it.

[strapi-cla]

All committers have signed the CLA.