feat(analysis): support typed PostgreSQL returning writes

[omer-cengel]

Summary

Add typed row results for supported PostgreSQL write statements so generated code can return database-generated identifiers and resulting rows through the existing query APIs.

Changes

• Analyze direct target columns and bare RETURNING * on supported INSERT, UPDATE, and DELETE statements declared as :one or :many.
• Preserve schema types, nullability, returned-column order, logical parameter order, and textual JDBC binding order.
• Reuse existing generated result records, positional row mappers, and query/queryMany runtime paths.
• Reject incompatible annotations, unsupported returning expressions, qualified wildcards, unknown columns, and excluded write shapes before generation.
• Cover generated-source compilation and live PostgreSQL behavior for generated identifiers, nullable results, repeated parameters, and empty or multi-row results.

Scope and non-goals

This change is limited to existing single-table write shapes with unaliased direct returned columns or bare *. It does not add computed or aliased returning expressions, qualified wildcards, upserts, multi-row or select-based inserts, joined writes, writable CTEs, generated-key APIs, transactions, new query types, or generalized expression analysis.