fix: distinguish custom SQL function mutations from CRUD in codegen

[pyramation]

Summary

matchMutationOperations in infer-tables.ts matched mutations purely by naming convention (delete{EntityName}, create{EntityName}). Custom SQL functions like delete_principal() / create_principal() are exposed by PostGraphile as deletePrincipal / createPrincipal — identical to CRUD naming — and were incorrectly claimed as CRUD mutations.

For Principal, the codegen then inferred PK constraints from DeletePrincipalInput { principalId: UUID } (the SQL function arg), produced select: { principalId: true } in the CLI delete handler, but PrincipalSelect only has id → TS error.

Fix: matchMutationOperations now checks the payload type before claiming a mutation as CRUD:

// New helper — CRUD payloads always return the entity:
//   DeleteUserPayload      → { user: User }        ✓ CRUD
//   DeletePrincipalPayload → { result: Boolean }    ✗ custom function
function isCrudMutation(field, entityName, typeMap): boolean {
  const payloadType = typeMap.get(getBaseTypeName(field.type));
  return payloadType.fields.some(
    f => f.name === lcFirst(entityName) && getBaseTypeName(f.type) === entityName
  );
}

Applied to all three CRUD checks (create/update/delete) and their ById/By* variants.

Reverts the earlier reverse-inflection workaround in table-command-generator.ts — the delete select logic is restored to the original pkFields.map(f => f.name: true) since PK constraint names now always come from real CRUD mutations where they match entity field names.

Generated principal.ts: no longer has handleDelete or handleGet (no CRUD delete/update). Commands: list, find-first, create.

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

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring