fix(database-pgsql): JSON-encode array bindings before passing to PDO

[michalbiarda]

Fixes #71

Summary

• Detect array values in PgSqlConnection::bindValues() and call json_encode() before binding, so json/jsonb columns receive a valid JSON string instead of the literal "Array"
• Add a regression test covering the array binding path

Test plan

• ./vendor/bin/pest packages/database-pgsql/tests/Connection/PgSqlConnectionTest.php — all 29 tests pass including the new one

🤖 Generated with Claude Code

[markshust]

Thanks @michalbiarda — good catch on this one. The PDO is_array blind spot is exactly the kind of silent failure that's hard to track down from the error message.

Maintainer changes

Tightened the encoder to match the loud-errors pattern already in use elsewhere in the framework:

• Use JSON_THROW_ON_ERROR | JSON_UNESCAPED_UNICODE to mirror EntityHydrator::encodeJson(). Without JSON_THROW_ON_ERROR, json_encode() silently returns false on encoding failures (NAN, INF, recursive references, malformed UTF-8) and emits only a PHP warning — the bound value becomes false/0 and the database write succeeds with the wrong data.
• Added ConnectionException::invalidArrayBinding() factory that includes the parameter name and the underlying JsonException as context/previous.
• Added a regression test for the failure path (NAN as an array value → ConnectionException with the right message).
• Added @throws ConnectionException to bindValues().

Rebased onto current develop, force-pushed to your branch. Full pgsql suite green (133 passing). Merging via merge commit.

Heads-up: same bug exists for MySQL

While in here I noticed MySqlConnection::execute() and query() just hand $bindings straight to $statement->execute(), so MySQL has the same array-to-"Array" silent corruption for JSON columns. Different scope (your ticket was pgsql-specific) and the fix shape would be different (MySQL doesn't have a custom bindValues() to extend), so I'll spin that up as a separate issue and credit this one as the source.