fix(netlify): support custom baseURL

[TheAlexLichter]

🔗 Linked issue

Resolves #1484
(happy to backport to v2 as well)

❓ 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

Similar to the Vercel and CF PR, this supports the base url for the netlify presets.

📝 Checklist

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

[pi0]

v2 is active branch can you please rebase? 🙏

Also have you externally verified changes?

[TheAlexLichter]

Yup, verified in a quick demo (with Nuxt). Happy to open-source & link it 👍🏻

• it works similar to fix(vercel): support custom baseURL #2464 and fix(cloudflare): support custom baseURL #2821

Also, would you consider a similar change for the default static build (due to nuxt/nuxt#30446 (comment)) and the difference between building the default static vs. vendor-specific with a base url?

[pi0]

Also, would you consider a similar change for the default static build (due to nuxt/nuxt#30446 (comment)) and the difference between building the default static vs. vendor-specific with a base url?

This would be a breaking change for static behavior at least. Depending on the deployment strategy, baseURL needs to be applied to the filesystem output or not (if the platform removes it).

Do you mind to as the first step creating a nitro-only minimal reproduction?