Fix prepared statements

[fabianfett]

Motivation

Currently Prepared Statements only work if they only use bindings that have the PostgresDataType text. The reason for this is that text has the same representation in text and binary form. For this reason Postgres does not need to know the datatype upfront.

Changes

• Allow users to specify the bindings datatypes explicitly. Fallback to unspecified.
• If binding datatypes are unspecified infer them from the first provided bindings
• Allow users to override the prepared statement name
• Add integration test that validates the behavior

[codecov-commenter]

Codecov Report

❌ Patch coverage is 84.61538% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 62.02%. Comparing base (85d189c) to head (738d0b7).
⚠️ Report is 60 commits behind head on main.

Files with missing lines	Patch %	Lines
...es/PostgresNIO/Connection/PostgresConnection.swift	40.00%	3 Missing ⚠️
Sources/PostgresNIO/New/PSQLTask.swift	83.33%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #455      +/-   ##
==========================================
- Coverage   62.05%   62.02%   -0.04%     
==========================================
  Files         124      125       +1     
  Lines        9971     9980       +9     
==========================================
+ Hits         6188     6190       +2     
- Misses       3783     3790       +7     

Files with missing lines	Coverage Δ
...nection State Machine/ConnectionStateMachine.swift	63.48% <100.00%> (ø)
...tion State Machine/ExtendedQueryStateMachine.swift	79.59% <100.00%> (ø)
...urces/PostgresNIO/New/PostgresChannelHandler.swift	84.31% <100.00%> (+0.02%)	⬆️
Sources/PostgresNIO/New/PreparedStatement.swift	100.00% <100.00%> (ø)
Sources/PostgresNIO/New/PSQLTask.swift	77.77% <83.33%> (-0.35%)	⬇️
...es/PostgresNIO/Connection/PostgresConnection.swift	42.28% <40.00%> (-0.20%)	⬇️

... and 2 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.