Upgrade Next.js, add experimental Next.js/Turbopack analyzer

[timneutkens]

Summary by cubic

Upgraded apps/web to Next.js 16.0.2-canary.23 and added an experimental Turbopack/Next bundle analyzer. Adjusted payment webhook API routes to keep raw request bodies for reliable signature validation.

• New Features

  • Added experimental-analyze script: turbo run copy-app-store-static && next experimental-analyze --serve.

• Bug Fixes

  • Webhooks (Alby, BTCPay Server, PayPal, Stripe) now set config.api.bodyParser = false locally to preserve raw body and prevent signature verification issues on Next 16.

^{Written for commit f779add. Summary will update automatically on new commits.}

[vercel]

@timneutkens is attempting to deploy a commit to the cal Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "Upgrade Next.js, add experimental Next.js/Turbopack analyzer". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

[github-actions]

This PR has been marked as stale due to inactivity. If you're still working on it or need any help, please let us know or update the PR to keep it active.