fix: sanitize rollup-generated filenames

[danielroe]

🔗 Linked issue

resolves nuxt/nuxt#12606
reverts #477

❓ 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 removes characters from rollup filenames that are excluded from valid URLs (see RFC 2396). As rollup-produced files may be consumed by browsers, this is one approach to provide broader ecosystem safety without requiring URL encoding.

I've also proposed this in a PR directly to rollup but there may be legitimate reasons for closing it, as this is relevant specifically to browsers rather than the node ecosystem. If accepted we can remove the implementation in this PR.

(Having said that I have also implemented for nitro as I feel most of these characters may also pose problems for filesystems, and in a worker target the filenames may also become URLs.)

📝 Checklist

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

[netlify]

✔️ Deploy Preview for nuxt3-docs canceled.

🔨 Explore the source changes: 17db2f8

🔍 Inspect the deploy log: https://app.netlify.com/sites/nuxt3-docs/deploys/618286c69b78190007341fed

[pi0]

This is a nice idea and we need sanitizers both for generated file names and export identifiers (instead of unreadable hashes we use). What do you think to move sanitizePath to mlly?