Add native boolean type support to QueryBinding

[coenttb]

Summary

This PR introduces proper boolean type handling in StructuredQueries to better support databases with native boolean types (like PostgreSQL) while maintaining backward compatibility with SQLite.

Problem

Previously, boolean values were always encoded as integers (0/1), which caused type mismatch errors when working with PostgreSQL's native BOOLEAN type:

column "isActive" is of type boolean but expression is of type bigint

Solution

• Add a new .bool(Bool) case to the QueryBinding enum
• Allow database drivers to handle boolean values appropriately for their specific database
• Maintain backward compatibility with SQLite

Changes

Core Features

• Add .bool(Bool) case to QueryBinding enum
• Update Bool's queryBinding to use .bool(self) instead of .int()
• Add boolean handling in debugDescription (returns "1"/"0" for SQLite compatibility)

SQLite Support

• SQLite driver converts .bool to integer (0/1) for compatibility
• All existing tests pass without modification

Trigger Support

• Add proper boolean handling in trigger statements

Additional Improvements

• Make iso8601String property public on Date extension
• Make quoted method public in Quoting extension
• These visibility changes allow database drivers to implement their own database-specific SQL rendering methods without duplicating utility functions

Impact

• ✅ Backward Compatible: SQLite continues to work exactly as before
• ✅ PostgreSQL Support: Native boolean types now work correctly
• ✅ Extensible: Other database drivers can implement their preferred boolean handling
• ✅ Type Safe: Maintains type safety throughout the library

Testing

All existing tests pass. The change is backward compatible and does not break existing SQLite-based code.

Related

This change enables proper PostgreSQL support in downstream libraries like swift-structured-queries-postgres.

[stephencelis]

@coenttb Thanks! Do you have time to open a SharingGRDB PR against this branch to see what needs to change? Unfortunately these kinds of breaking changes will need to be coordinated.

[coenttb]

@stephencelis Done! SharingGRDB PR opened at #141 with minimal changes needed. Just adding the .bool case handling.

[stephencelis]

Somehow you opened dual 141s 😄 https://github.com/pointfreeco/sharing-grdb/pull/141

[stephencelis]

Sorry for the minor nit, but we like to alphabetize for the most part (invalid is an outlier which is why it comes last).

[coenttb]

I considered that and originally put it there, too. Was thinking it might signal 'this is not an sql type' to put it at the bottom.

[stephencelis]

@coenttb We intended to merge this soon. Any reason why you closed it?

[coenttb]

Didn't intentionally do it. But I would also advise against adopting this, and think database adapters through a little more. For my use, I decided to fork the repo and rewrite it for just Postgres. There were more foundational incompatibilities that I came across. I'm a little swamped, but from memory the primary blocking factor was in the Table protocol. Additionally, I had to make some edits in the macros as Postgres handling for nil IDs had to be done a little differently. You can check my progress at swift-structured-queries-postgres.

[stephencelis]

While we do want to explore that soon, we think the tools are stable enough to cut a 1.0 relatively soon and think these gaps should be handled. We can wait for 2.0 for a better version in the future.