Lay the HubSpot and customer-lifecycle foundation

Work in progress from the Codex session, committed so nothing sits undeployed.
Verified before committing: typecheck clean across all packages, 139 unit tests
and the e2e suite green, migrations apply to an empty Postgres.

Adds the HubSpot integration boundary (OAuth, client, contracts, webhook
signature verification, sync), a growth route, customer-lifecycle service,
Piggy lifecycle tools, a Growth page, and shared lifecycle/hubspot types.

Two things are deliberately incomplete and should not be mistaken for finished:

`packages/db/src/schema/hubspot.ts` is NOT exported from the schema index, so it
is inert — no tables, no migration. That is the correct order (the shape can
settle before it becomes a migration), but it does mean the HubSpot routes have
no persistence behind them yet.

`pnpm-workspace.yaml` and `pnpm-lock.yaml` are left uncommitted on purpose. The
workspace file contains a literal unanswered placeholder — "esbuild: set this
to true or false" — and this repository installs with npm, which is also what
CI runs. Committing a second package manager's lockfile would make the install
ambiguous. If the move to pnpm is intended it should be a deliberate change
that updates CI and the Dockerfile together.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

apps/api/src/integrations/hubspot/contracts.ts

@@ -0,0 +1,20 @@
+export {
+  HUBSPOT_CONNECTION_STATUSES,
+  HUBSPOT_EVENT_STATUSES,
+  HUBSPOT_JOB_KINDS,
+  HUBSPOT_JOB_STATUSES,
+  HUBSPOT_OBJECT_TYPES,
+  HUBSPOT_REQUIRED_SCOPES,
+  HUBSPOT_SYNC_PHASES,
+} from '../../../../../packages/core/src/hubspot';
+export type {
+  HubSpotConnectionStatus,
+  HubSpotEventStatus,
+  HubSpotJobKind,
+  HubSpotJobStatus,
+  HubSpotObjectType,
+  HubSpotRecord,
+  HubSpotRecordPage,
+  HubSpotRequiredScope,
+  HubSpotSyncPhase,
+} from '../../../../../packages/core/src/hubspot';