refactor: split out api types

[danielroe]

🔗 Linked issue

nuxt/nuxt#13920

❓ 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 is a follow-on from #1021, adding support for splitting explicit nitropack augmentations from auto-import types (which affect the global scope). This should mean that a consuming framework, like Nuxt, can pull in types/nitro-augmentations.d.ts safely for typed $fetch without also adding the auto-import types to the global namespace.

I've implemented this (with /// <reference />) to keep the change backward-compatible in case users are explicitly referencing nitro.d.ts, but with this change nitro-augmentations.d.ts also becomes part of the public API (so better naming ideas are definitely welcome)...

📝 Checklist

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

[codecov]

Codecov Report

Merging #1027 (e762aa5) into main (b495675) will decrease coverage by 0.40%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #1027      +/-   ##
==========================================
- Coverage   67.59%   67.20%   -0.40%     
==========================================
  Files          62       62              
  Lines        6259     6287      +28     
  Branches      707      707              
==========================================
- Hits         4231     4225       -6     
- Misses       2015     2049      +34     
  Partials       13       13              

Impacted Files	Coverage Δ
src/build.ts	39.17% <0.00%> (-4.44%)	⬇️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[pi0]

Nice change. Can we with the same PR, split to explicit nitro-imports.d.ts too? (then nitro can reference both)

(further, i think we might split nitro-routes and nitro-config too. logic in same file is getting longer over the time)