feat!: migrate to vite 3

[danielroe]

🔗 Linked issue

resolves #492

❓ 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 like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This PR upgrades Bridge to Vite 3.

There are quite a few fixes/refactors to note, including some other vite fixes in Nuxt 3 that we're hereby porting back to Bridge. But particularly worth observing:

1. We remove the workaround where we move build output files around, instead modifying chunk names.

2. We remove our runtime URL implementation, using new Vite support from feat: experimental.buildAdvancedBaseOptions vitejs/vite#8450.

   We'll track the development of this feature quite closely as it moves from experimental into the mainstream, but it will not break in a minor version so the current version constraint is safe.

👉 Migration

Vite 3 is a major release with its own breaking changes. Users should read through the migration guide and make any updates necessary. (Other libraries may also have to be updated to work with Vite 3.)

There are no Nuxt-specific changes that users will need to make.

📝 Checklist

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

[danielroe]

@pi0 - note stub fix for now - please do let me know if you have a better idea.