This PR fixes two issues with PostgreSQL boolean handling:

1. Emulated prepares bug: When PDO::ATTR_EMULATE_PREPARES is enabled, boolean values cause errors
2. Raw SQL bug: Methods like toRawSql() output 1/0 instead of true/false

Problem

When using PostgreSQL with PDO::ATTR_EMULATE_PREPARES => true, queries with boolean columns fail:

  SQLSTATE[42804]: Datatype mismatch: 7 ERROR:
  column "is_active" is of type boolean but expression is of type integer

This happens because:

• Base Connection::prepareBindings() converts booleans to 1/0
• PostgreSQL requires true/false literals, not integers
• With emulated prepares, PDO embeds values directly into SQL string

This is a known Laravel bug that affects Hyperf too.

Solution

PostgreSqlConnection.php:

• Override prepareBindings() to convert booleans to 'true'/'false' when emulated prepares enabled
• Override escapeBool() to return 'true'/'false' for raw SQL methods

PostgreSqlSwooleExtConnection.php:

• Override escapeBool() to return 'true'/'false' for raw SQL methods

References:

• Cast from bool to int breaks PostgreSQL queries laravel/framework#37261
• Add PDO::ATTR_EMULATE_PREPARES = true support laravel/ideas#2005
• Should Laravel database connections use cached prepared statements? laravel/framework#46808

Laravel's PostgresConnection has the same escapeBool() fix:
https://github.com/laravel/framework/blob/12.x/src/Illuminate/Database/PostgresConnection.php#L42-L45

Tests Added

New file: PostgreSqlConnectionTest.php

• testPrepareBindingsConvertsBooleanToStringWhenEmulatedPreparesEnabled
• testPrepareBindingsConvertsBooleanToIntegerWhenEmulatedPreparesDisabled
• testEscapeBoolReturnsPostgresLiterals

Added to: PostgreSqlSwooleExtConnectionTest.php

• testEscapeBoolReturnsPostgresLiterals