refactor(schema): introduce future and features namespace

[danielroe]

🔗 Linked issue

❓ 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)
• 🧹 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 introduces new features and future namespaces.

• features is for turning on/off specific features within Nuxt that are meant (and will continue) to be configurable but are not experimental.
• future is for early opting-in to new features that are expected to become default in a future (possibly major) version of the framework.

I've also moved inlineSSRStyles, noScripts, and typescriptBundlerResolution from the previous namespace to new namespace, with backwards compatibility (though type errors will be shown in user projects).

📝 Checklist

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

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[nuxt-studio]

✅ Live Preview ready!

Name	Edit	Preview	Latest Commit
Nuxt Docs	Edit on Studio ↗︎	View Live Preview	66cfb0c

[codspeed-hq]

CodSpeed Performance Report

Merging #24880 will degrade performances by 34.94%

_{⚠️ No base runs were found}

_{Falling back to comparing refactor/features (5d67a70) with main (1a9fb57)}

Summary

⚡ 1 improvements
❌ 1 regressions
✅ 6 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	main	refactor/features	Change
⚡	minimal test fixture (types)	136.3 ms	42.7 ms	×3.2
❌	minimal test fixture	39.2 ms	60.3 ms	-34.94%

[danielroe]

Looks like this is might be a bug in untyped: 23e98be. cc: @pi0