chore: separate build commands for core and app

[ThangHuuVu]

Reasoning 💡

Separate build command for next-auth and next-auth-app.

Checklist 🧢

• [ ] Documentation
• Move emitDeclarationOnly to next-auth only
• Tests
• Ready to be merged

Affected issues 🎟

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/nextauthjs/next-auth/7L8Z4CAub9UCwtdwKmidmaEKWfty
✅ Preview: https://next-auth-git-fork-thanghuuvu-chore-update-bu-8afe80-nextauthjs.vercel.app

[Deployment for 4c8dafb canceled]

[balazsorban44]

I don't remember the context here. Could you help? I think we should keep the build command for CI/CD purposes, but we only need to build the core app and the adapter packages right now (later on other framework packages like @next-auth/svelte etc), not the docs (it has its own pipeline at Vercel) or the dev app (never published)

[ThangHuuVu]

@balazsorban44 You mentioned that it's not very common to build app, so I thought this should add some improvements to the pipelines.

I think we should keep the build command for CI/CD purposes, but we only need to build the core app and the adapter packages right now (later on other framework packages like @next-auth/svelte etc), not the docs (it has its own pipeline at Vercel) or the dev app (never published)

I just updated the build command accordingly 👍

[balazsorban44]

Nice! Thank you!