fix(select-query-parser): select left join and array instead of objects result types

[avallete]

What kind of change does this PR introduce?

This PR improves the TypeScript typings generated by the SQL query parser, fixing issues with inferred types for certain !left joins and relationship queries (e.g., created_by:users(*)).

What is the current behavior?

Currently, for certain queries, the inferred types for relations are incorrect. For instance, the type may be inferred as {}[] when the runtime result is a single object {}.

Related issues
#546
supabase/supabase#29086

What is the new behavior?

This PR updates the select-query-parser to handle these cases more accurately by:

• Extending the handling logic for the !left operator, similar to the existing logic for the !inner operator.
• Returning a single object for relationships when the runtime result is also a single object.

Additional context

The TypeScript code in select-query-parser is quite complex. I would appreciate a thorough review of this fix.
Additional tests have been added to cover both runtime and typing scenarios. This helped uncover more edge cases, some of which still need further solutions.

Known Issues:

Currently, there is no distinction between possibly nullable and non-nullable results for zero-to-one or one-to-one relations. To handle this properly, the PR always returns null as a possible option. However, a more accurate solution would involve enhancements like adding an isOneToOne option in Relationships that marks foreign keys as nullable or non-nullable based on columns[] type definitions.

PS

Also took the chance to fix the CI workflow by replacing the deprecated docker-compose with docker compose command.

[soedirgo]

Thanks! I think this fixes supabase/supabase#29086 but not #546 - will investigate that separately

[github-actions]

🎉 This PR is included in version 1.16.1 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀