Open
Description
For options that are specific to one component, we shouldn't require a new custom env (custom env make sense when they are used for multiple components). Custom env are linked to a specific workspace and are not automatically imported when you import a specific component.
This would for example allow users to set specific global scripts and styles for all of the compositions.
The options should be similar to what we can find in angular.json files.