chore: run test suite on windows

[sandros94]

🔗 Linked issue

Related: nuxt/ecosystem-ci#15

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ 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

This both fixes the development of Nuxt UI on windows as well as run CI tests on windows-latest too

TODO

• remove depending on shell-emulator
• remove depending on DEV = true env var in scripts
• update ci
• fix nuxt-module-build on windows
  • issue while re-exporting the component types (upstream Module build results in "error TS2307: Cannot find module or its corresponding type declarations." module-builder#519)
  • EOF issues with form types (unrelated)
• component's template are not transpiled (upstream mkdist#281)

📝 Checklist

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

[pkg-pr-new]

npm i https://pkg.pr.new/@nuxt/ui@3479

commit: 79daffd

[nuxthub-admin]

✅ Deployed ui3

Deployed ui3 79daffd to preview

🔗	fix-windows-dev.ui-6q2.pages.dev
📌	10d5430b.ui-6q2.pages.dev
📱	View QR Code

📋 View deployment logs

[sandros94]

@danielroe upgrading to @nuxt/module-builder@1.0.0-alpha.1 did indeed solve the issue (alongside an upstream fix from nuxt-component-meta).

unbuild v3 works great but this also introduced mkdist v2, which atm doesn't support typescript in templates (mkdist#281). Is it safe to pin mkdist to v1.6 while using unbuild v3 and moudle-builder v1 alpha?