feat: move nitro integration into separate vite plugin package

[goetzrobin]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/analogjs/analog/blob/main/CONTRIBUTING.md#-commit-message-guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

Which package are you modifying?

• vite-angular-plugin
• astro-angular
• create-analog
• router
• platform
• content

What is the current behavior?

Currently the platform package includes a plugin that enables nitro support for development and production.
The idea is to move this plugin into its own package and ultimately allow users to pick a backend of their choice.

Issue Number: #318

What is the new behavior?

nitro integration is moved to a separate package

Does this PR introduce a breaking change?

• Yes
• No

Not the way it is implemented right now. We are making the platform package depend on the new nitro package and include the nitro plugin as part of the platform plugin array

Other information

Open questions:

• do we want to share the Options/PrerenderOptions interfaces and move them in a separate package? Currently, I just copied and pasted them to get started...
• do we want to include the nitro plugin by default or leave it up to the user?
• do we want to remove analog references in the nitro plugin, e.g. build output folder is analog currently?

Let me know what you think!

[netlify]

✅ Deploy Preview for analog-app ready!

Name	Link
🔨 Latest commit	154f2f2
🔍 Latest deploy log	https://app.netlify.com/sites/analog-app/deploys/64396c25af4e43000846e028
😎 Deploy Preview	https://deploy-preview-341--analog-app.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[netlify]

✅ Deploy Preview for analog-docs ready!

Name	Link
🔨 Latest commit	154f2f2
🔍 Latest deploy log	https://app.netlify.com/sites/analog-docs/deploys/64396c26552dc9000743f81a
😎 Deploy Preview	https://deploy-preview-341--analog-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[netlify]

✅ Deploy Preview for analog-blog ready!

Name	Link
🔨 Latest commit	154f2f2
🔍 Latest deploy log	https://app.netlify.com/sites/analog-blog/deploys/64396c2666d10e000884d876
😎 Deploy Preview	https://deploy-preview-341--analog-blog.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[goetzrobin]

@brandonroberts I cannot get the e2e tests for the plugin to pass... I think it is due to nrwl/nx#15263. If you have time to take a look at this that would be awesome. I am a little bit at my wits end because I see other PRs pass 😭 I disabled them for now just to see if everything else works fine

[brandonroberts]

@goetzrobin no problem. Seeing as how all the other tests pass the preview builds are working, I think its good to go. Maybe it will be resolved when we publish the package.