test(codegen): add vector schema integration test for plugin-injected fields

[pyramation]

test(codegen): add vector schema integration test for plugin-injected fields

Summary

Follow-up to #791. Adds an integration test that exercises the full codegen pipeline (FileSchemaSource → runCodegenPipeline → generateOrm) against a hand-crafted vector (pgvector) schema fixture, validating that plugin-injected condition fields, orderBy values, and transitive types appear in the generated TypeScript output.

The transitive type resolution bug fix (for enum types like VectorMetric) and the VectorFilter scalar filter type have been upstreamed to #791. This PR now contains only the test infrastructure.

Changes

1. New schema fixture — graphql/codegen/examples/example-vector.schema.graphql: a PostGraphile-style schema with Contact/Document entities, Vector scalar, VectorNearbyInput, VectorMetric enum, and plugin-injected condition/orderBy fields.

2. Integration test — vector-codegen-integration.test.ts (13 test cases): verifies pipeline table inference, typeRegistry contents, and generated ORM output including Vector→number[] mapping, condition fields, orderBy values, VectorNearbyInput/VectorMetric types, and backwards-compatible CRUD/filter types.

Updates since last revision

• Updated base PR reference from fix(codegen): include plugin-injected fields in condition and orderBy types #789 → fix(codegen): include plugin-injected fields in condition/orderBy types + VectorFilter #791 (clean branch, free of third-party commits).
• Merged upstream VectorFilter changes (Vector → VectorFilter in SCALAR_FILTER_MAP, VectorFilter config with equality/distinct operators). This adds a VectorFilter unit test and 14 updated snapshots (mechanical — VectorFilter added to always-generated scalar filter types).
• Full suite now at 320 tests passing; workspace build succeeds.

Review & Testing Checklist for Human

• Check the fixture schema is realistic: example-vector.schema.graphql is hand-crafted, not captured from a real PostGraphile introspection. Verify the condition type shape (plugin-injected embeddingNearby alongside column fields) and orderBy enum values match what VectorSearchPlugin actually produces. If the real plugin output differs (e.g., different field naming or type wrapping), these tests would pass but not catch real-world issues.
• String-matching assertions: The integration tests use toContain / toMatch on generated output strings. Confirm there are no false positives from matching substrings in unrelated sections of the generated file (e.g., "embeddingNearby" appearing in a comment vs. an actual field declaration).
• Run pnpm test in graphql/codegen/ and pnpm build at workspace root to confirm all tests pass and build succeeds.

Notes

• 13/13 integration tests pass locally; full suite (320 tests) passes; workspace build succeeds.
• Unused imports cleaned up from initial commit.
• Link to Devin session
• 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