Create Block: Streamline experience for working with multiple blocks and shared assets

[gziolo]

Today, @wordpress/create-block is too optimized for the specific use case of developing a single block as a WordPress plugin. Things quickly get more complicated when another block is needed or a custom JavaScript is integrated to extend the block editor. This issue will track necessary enhancements and bug fixes to resolve the outstanding problems that need to be addressed to streamline the experience.

Related tasks

• Create Block: Optimize the default template for multiple blocks case #68175
• Create Block: Add multi variant #67886
• Create Block: Allow external templates to customize more fields #68193
• Create Block: Support Custom Prompts in External Templates #67806
• WP Scripts: Automatically detect entry points for the default JS and CSS files #66466
• When defining the JS and CSS assets in the block.json file, we could change the strategy. Developers, when using the source directory should only reference source files. The build process would detect them as entry points and update block.json accordingly so everything is magically configured inside the build folder.
• Improve auto-injecting the webpack runtime chunk into block.json when viewScript defined.