feat: @nuxt/eslint integration workflow

[adhamfarrag]

🔗 Linked issue / Discussion

❓ 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

Latest Nuxt Eslint module integration workflow, from installation to file creation to modifying VSCode Eslint settings.
It also follow simplifed process where users only gets asked single question regarding activating Dev Server Checker and installing vite-plugin-eslint2 under the hood.

Will test the new flow with users and based on feedback I will either revert or migrate other configuration commands.

📝 Checklist

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