feat(cli): add support for the `init` command

[vaporwavie]

What's the purpose of this pull request?

Adds initial support for the init command, which aims to boostrap (and scaffold) Discovery from the starter.store template.

How it works?

It creates a new oclif command that wraps the discovery composition using degit.

How to test it?

• Clone https://github.com/vtex/store-monorepo
• Recommended: checkout to the faststore-cli-integration branch
• On package.json change the build version of @faststore/cli to the last one available in our CodeSandbox CI
• Run yarn again to refresh the modules
• Run yarn fsp discovery init
• Notice that discovery/ will be created and available for usage.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

| Name | Status | Preview | Comments | Updated (UTC) | | :--- | :----- | :------ | :------- | :------ | | **faststore-site** | ⬜️ Ignored ([Inspect](https://vercel.com/faststore/faststore-site/ChybnDszPkedqh9Mp7ffzRmMTP55)) | [Visit Preview](https://faststore-site-git-feature-discovery-init-command-faststore.vercel.app) | | Jul 10, 2024 0:57am |

[codesandbox-ci[bot]]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[vaporwavie]

@lariciamota @gvc I'll do a file move commit, so /commands/discovery/init.ts becomes /commands/init.ts to make it consistent with the existing commands.

PS: This is also considering that the platform CLI will already prefix discovery, so this redundancy is not needed.

[gvc]

@eduardoformiga the goal is to have people use only the fsp CLI directory as their main CLI and only go to the faststore CLI if they need something specific on the discovery part.