refactor: restructure cli commands to support different frameworks templates

[MuhammadM1998]

🔗 Linked issue

#570

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

POC of #570. This PR just extracts the vue-specific code init, add, diff commands into their respective commands in commands/frameworks/vue folder and update the imports accordingly. No other changes were made for easier reviewing.

Remarks:

• getConfig has been extracted to its separate file too because in the Nuxt module we'd read the config differently (think reading components config from nuxt.config instead of components.json). Hence it's extracted to a reusable function to be used in all commands when needed.
• We export the same vue commands for nuxt to ensure everything works as expected. Next step is creating nuxt-specific commands and use those instead.

📸 Screenshots (if appropriate)

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[MuhammadM1998]

@sadeghbarati Tests are passing but can you help confirming everything works as expected 🙏

[sadeghbarati]

Sure, I appreciate the effort you put into ❤️‍🔥

Will test tomorrow 🙌

[sadeghbarati]

https://stackblitz.com/edit/vitejs-vite-1fjqkm?file=package.json

@MuhammadM1998 Sry for the late test, I tested the CLI the seems to have problem with the add command
init command is working well but add command still repeat the init command even though the component.json is exists

[MuhammadM1998]

Thanks for testing 🙏 I'll see whats wrong and retest

[MuhammadM1998]

@sadeghbarati It was always running promptForConfig which should only run in init. It's fixed now and running as expected.