build: add ARG NODE_OPTIONS to dockerfile for memory allocation

[Gatuflow]

Summary

This pull request is proposed as a way to facilitate the building process of the docker image. On some devices with lower resources, such as the laptop this is sent from, the default Node.js memory limit returns a FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory. When trying to pass the build command with an argument NODE_OPTIONS to increase that limit, it gets swiftly ignored.

Type of Change

• Bug fix
• New feature
• Refactoring / code quality
• Documentation
• Other (describe): Build / infrastructure configuration

Target and Risk

• Feature/fix PR into development
• Release promotion from development into staging
• Production promotion from staging into main
• Changes auth, billing, migrations, tenant isolation, deployment, or secrets

Risk and blast radius:

Rollback or recovery plan:

Testing

• pnpm type-check passes
• pnpm build succeeds
• Tested manually in a local dev environment
• Added/updated E2E tests (if applicable)
• Preview or staging smoke test completed (for promotions)

Screenshots

N/A (No UI impacts)

Checklist

• Code follows the existing style (TypeScript, Tailwind, tRPC patterns)
• No hardcoded secrets or credentials
• Database changes include schema updates in packages/db/schema/
• Database changes use backward-compatible expand/contract sequencing
• Existing migration SQL and snapshots were not edited
• New API endpoints include Zod validation and role-based access checks
• Deployment, workflow, auth, billing, and migration changes have an explicit owner review

[vercel]

Someone is attempting to deploy a commit to the evangauer's projects Team on Vercel.

A member of the Team first needs to authorize it.