[#121] Move Vite folder to packages

[bterone]

• Close Move the /vite-template folder into the /packages folder  #121

What happened 👀

✅ Moved Vite template to under /packages directory
🔴 Removed lerna bootstrap command as it has been deprecated and now uses the package.json workspaces config 😄

✔️ Since moving the vite template to packages, the package-name %APP_NAME% is no longer valid. We've renamed to nimble-vite-template and we replace when generating the files

Insight 📝

🙌 With this PR, we allow for copying template files from the packages folder. This is only for the vite-template currently, and if there is NO template reference provided when running the generate command

For now we keep both Copying template files strategy and Downloading template strategy to keep options open in the future

🔨 Currently we're using @oclif/test which uses mocha and chai under the hood. We want to update to use jest so we can test all future changes following #116

Proof Of Work 📹

Tests pass 🎉

[malparty]

Small early suggestions 😇

[malparty]

Suggested change

	CliUx.ux.info('Copying template source files...');
	CliUx.ux.info('Copying ${selectedTemplate} template source files...');

Should/Can we add the template name in the log? 👀

[malparty]

Suggested change

	return this.downloadTemplateRepository(options)
	.then(() => this.extractDownloadedTemplateFolder(options))
	.then(() => this.renameFolder(options))
	.then(() => this.cleanTemporaryFiles(options));
	await this.downloadTemplateRepository(options);
	await this.extractDownloadedTemplateFolder(options);
	await this.renameFolder(options);
	return await this.cleanTemporaryFiles(options);

Long time I haven't dealt with async JS, but as far as I remember, it acts the same but avoids the chained call (stack trace remains cleaner).

[bterone]

Sure, I wanted to keep changes to a minimum to make it easier to review, however I can change this 👍 😄

[bterone]

Fixed in 9f8df06 @malparty 🙌