feat: add description prompt and validation for project scaffolding

[Priyanshu-001]

Context

Chrome Web Store mandates the description field in the manifest (reference), although apparently it is not properly validated. Regardless, it is required as per the reference, and I propose we should add it.

Side note

if package description is not present currently webstore apparently starts repeating overview adding ss as proof.

Note I have added the overview line only once.

This is how the Chrome Web Store displays the extension when no description is provided:

this happened with me and spend hours figuring this out. Hopefully this PR will save someone else time.

changes

• The CLI now prompts the user for an extension description.
• A static default description is provided.
• The description is stored in package.json.
• The description is referenced from manifest.config.js/ts

Testing Screenshots

PS - I have added UTs and tested locally on my windows machine. If there is any more requirements please let me know thanks

[changeset-bot]

⚠️ No Changeset found

Latest commit: fee72db

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[FliPPeDround]

wow，thanks