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

El issue no menciona archivos, pruebas ni puntos de entrada. Empieza por localizar el flujo existente de creación de componentes de bloque y determina dónde se seleccionarían y generarían la opción Doc-Based, la carpeta del bloque y los fragmentos JSON de component-definition/component-model. Se considera terminado cuando los usuarios pueden elegir Universal Editor o Doc-Based y recibir el esqueleto de carpeta y los fragmentos JSON correspondientes.

Escrito por el modelo de indexación a partir del texto del issue.