feat: Generator CLI support

[jmuzina]

Done

Creates a prompting module that allows generators to request and read CLI input. Switches the generator to use CLI input only.

This will allow the generator to be executed programmatically, enhancing its testability.

QA

• bun i
• yo @canonical/canonical-ds:component - see that the generator now fails due to missing required positional argument
• yo @canonical/canonical-ds:component path/to/button - see that the generator creates a default button component
• yo @canonical/canonical-ds:component path/to/button --withStories --withStyles - see the generators also includes storybook and style files
• yo @canonical/canonical-ds:component --help - see the generator displays input parameter help

PR readiness check

• PR should have one of the following labels:
  • Feature 🎁, Breaking Change 💣, Bug 🐛, Documentation 📝, Maintenance 🔨.
• All packages define the required scripts in package.json:
  • All packages: check and check:fix.
  • Packages with a build step: build.

Screenshots

[advl]

In general, while I support the approach, I am skeptical of the quantity of code required to have the two modes working together.

It seems we are adding a lot of custom code to implement a mixin-like functionality, that is likely outside of the domain of this package.

Trying to reduce complexity, I would recommend :

• either trying to upstream such logic directly to yo,
• or reconsidering making a custom generator (in a separate package)
• or implementing cli mode as default, without interactive mode.

[bartaz]

I guess "yeoman-way" is to use config files if you don't want interactive prompts: https://yeoman.io/authoring/storage

[advl]

If we go for cli only, we can get rid of the prompting helpers and keep the generator to one file using this.argument