🐛 Fix nested object filtering in JSONB WHERE clauses

[evoludigit]

Summary

• Fixed incorrect SQL generation for nested object filters in GraphQL WHERE clauses
• Nested filters now correctly generate JSONB paths like data -> 'machine' ->> 'id' instead of accessing fields at root level

Problem

When using nested object filters in GraphQL WHERE clauses with JSONB-backed tables, FraiseQL was generating incorrect SQL that didn't properly handle the nested object path. This caused filters to fail silently and return unfiltered results.

Before (incorrect):

WHERE (data ->> 'id') = '01513100-0000-0000-0000-000000000066'

After (correct):

WHERE (data -> 'machine' ->> 'id') = '01513100-0000-0000-0000-000000000066'

Changes

• Modified where_generator.py to pass parent_path through the to_sql() method chain
• Added _build_nested_path() helper function for cleaner path construction
• Updated the DynamicType Protocol to include the new parameter
• Fixed logical operators (AND, OR, NOT) to also pass parent_path
• Enhanced tests to validate correct JSONB path generation
• Added deep nesting test coverage (3+ levels)
• Updated existing test that expected the old (incorrect) behavior

Test plan

• All existing tests pass (3283 tests)
• New test validates correct nested path generation
• Deep nesting (3+ levels) test added and passes
• Ruff linter passes
• No regressions introduced

🤖 Generated with Claude Code