feat: support framework config

[pi0]

🔗 Linked issue

❓ 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

This adds a new advanced framework configuration allowing meta-frameworks such as Nuxt to declare their meta-data that can be passed to the underlying presets or reflect nitro behavior when needed. The default is framework: { name: 'nitro', version } when using nitro CLI/API directly.

Update: Draft status is to check if we might need "multi" framework information (having version info about both nitro and nuxt for example)

📝 Checklist

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

[codecov]

Codecov Report

Merging #1843 (f390a3e) into main (e8fa771) will increase coverage by 0.46%.
Report is 13 commits behind head on main.
The diff coverage is 100.00%.

❗ Current head f390a3e differs from pull request most recent head 0304bf5. Consider uploading reports for the commit 0304bf5 to get more accurate results

@@            Coverage Diff             @@
##             main    #1843      +/-   ##
==========================================
+ Coverage   51.94%   52.40%   +0.46%     
==========================================
  Files         174      170       -4     
  Lines       12035    11790     -245     
  Branches      913      907       -6     
==========================================
- Hits         6252     6179      -73     
+ Misses       5686     5515     -171     
+ Partials       97       96       -1     

Files	Coverage Δ
src/options.ts	96.40% <100.00%> (+0.04%)	⬆️
src/types/nitro.ts	100.00% <100.00%> (ø)

... and 15 files with indirect coverage changes

[danielroe]

Nice idea! What are you thinking that presets will do with this info? I'm sure you've thought about it, but is there a danger that this ends up coupling Nitro presets too closely to upstream frameworks?

[pi0]

I think the main reason would be displaying info in output meta. I also agree that there should be absolutely no differences when coupled with an upstream framework to have a platform behavior other than displaying.