chore: regenerate SDK packages from updated schemas

[pyramation]

Summary

Regenerates all three SDK packages (constructive-sdk, constructive-react, constructive-cli) from the updated .graphql schema files in sdk/constructive-sdk/schemas/ using the schemaDir-based codegen pipeline.

Schemas processed: admin, app (empty/skipped), auth, objects, public

Key changes reflected in the regenerated output:

• private.graphql schema removed (was 44k+ lines); its types are now consolidated
• searchTsv: FullText removed from UserInput/UserPatch mutation inputs (tsvector columns are auto-populated by DB triggers and should not be manually set)
• SEARCH_TSV_ASC/SEARCH_TSV_DESC removed from UserOrderBy enum (ordering by raw tsvector is meaningless)
• Minor reordering of generated fields, imports, and documentation entries (non-functional, due to codegen determinism changes)

All generated code compiles cleanly (pnpm build passes). CI is green (41/41).

Review & Testing Checklist for Human

• Verify the schemas in sdk/constructive-sdk/schemas/ are correct and complete — these are the source of truth for all generated SDK code. The private.graphql removal is the biggest change; confirm nothing was lost that should have been kept.
• Spot-check the public schema-types and ORM — public has 103 tables and is the largest target. Verify the generated types and ORM operations look correct for a few key tables (e.g., User, Database, App).
• Confirm searchTsv removal from mutation inputs is intentional — this aligns with the graphile-build-pg rc.8 upgrade (PR fix: upgrade graphile ecosystem to latest RC versions with compatibility fixes #820) where tsvector columns are now hidden from insert/update. If any downstream consumer relies on setting searchTsv manually, this would be a breaking change.

Notes

• All output is auto-generated via pnpm generate in each SDK package. No hand-written code was modified.
• The app.graphql schema produced no tables (empty schema) and was skipped by the generator, as expected.
• The field/command reordering throughout the diff is cosmetic — the codegen produces deterministic but not necessarily stable ordering across runs.

Link to Devin session: https://app.devin.ai/sessions/7dae13db67bc4cc9b971e75984be2187
Requested by: @pyramation