fix: generate TypeScript types for custom scalar filter types (EmailFilter, ImageFilter, UploadFilter)

[pyramation]

Summary

Fixes TS2552: Cannot find name 'ConstructiveInternalTypeEmailFilter' (and ImageFilter, UploadFilter) build errors in SDK codegen output.

Root cause: collectFilterExtraInputTypes() skipped fields matching table column names, assuming only plugin-injected fields could reference non-standard filter types. But regular columns with custom scalar types (e.g., ConstructiveInternalTypeEmail) also have custom filter types in the schema (ConstructiveInternalTypeEmailFilter) that need TypeScript definitions generated.

Fix: Remove the tableFieldNames skip. Instead, check ALL filter fields (except and/or/not) and collect any referenced type that isn't a known GraphQL scalar or an already-generated base filter type (BASE_FILTER_TYPE_NAMES).

Review & Testing Checklist for Human

• Verify no duplicate type declarations: Removing the tableFieldNames guard means relation-derived filter fields (e.g., memberByContactId: MemberFilter) will also be collected. These should be de-duplicated downstream by tableCrudTypes in generateCustomInputTypes, but verify no duplicate export type/interface declarations appear in generated output.
• Verify BASE_FILTER_TYPE_NAMES covers all SCALAR_FILTER_CONFIGS names: The new guard relies on BASE_FILTER_TYPE_NAMES (from scalars.ts) to skip already-generated scalar filter types. If any name in SCALAR_FILTER_CONFIGS is missing from BASE_FILTER_TYPE_NAMES, it would be collected and potentially duplicated.
• Test against real schema: The unit tests (317 pass) use a simple example schema without custom scalar types. Regenerate the SDK for constructive-db (admin/migrate/public schemas) to confirm ConstructiveInternalTypeEmailFilter, ConstructiveInternalTypeImageFilter, and ConstructiveInternalTypeUploadFilter are now generated and the build succeeds.

Notes

• The collectConditionExtraInputTypes() function (for condition types) still has the tableFieldNames guard. Condition fields for standard columns use raw scalar types (not custom filter types), so the same bug doesn't apply there. However, if custom scalar condition types emerge in the future, the same fix may be needed.

Link to Devin session: https://app.devin.ai/sessions/745d2d10b699452091e24131ba5edef2
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 and CI monitoring