Block Generation for Universal Editor

### Is your enhancement related to a problem? Please describe.

The current block component creation is based on the doc-based EDS approach. It lacks the ability to generate JSON configuration code snippets for component-definition and component-models in the universal editor. This enhancement aims to address this issue.

### Describe the solution you would like

The proposed solution is to allow users to choose between Universal Editor or Doc-Based before creating a block component. This choice will guide the creation of the block folder and the code skeleton for the component definition and model JSON snippets.

### Describe alternatives you have considered

An alternative considered is to abstract component configuration to the block level. This involves creating separate model and definition JSON files in the block folder. This could enhance the developer experience, especially when using the Copilot extension, as it would automatically create the block's respective JSON files.

### Additional context

L’issue ne nomme aucun fichier, test ou point d’entrée. Commencez par localiser le flux existant de création de composants de bloc et déterminez où seraient sélectionnés et générés le choix Doc-Based, le dossier du bloc et les snippets JSON de component-definition/component-model. Le travail est considéré comme terminé lorsque les utilisateurs peuvent choisir Universal Editor ou Doc-Based et recevoir l’arborescence de dossiers ainsi que les snippets JSON correspondants.

Rédigé par le modèle d'indexation à partir du texte de l'issue.