fix: prepared statement could return error 'This ResultSet is closed'

[olavloite]

Executing a query using a server side prepared statement in a read/write transaction
would return the error "This ResultSet is closed". This happened because the result
set that was used to describe the statement would be closed before the actual result
was sent.

Fixes #278

[codecov]

Codecov Report

Merging #279 (01f1563) into postgresql-dialect (fe56a53) will increase coverage by 0.00%.
The diff coverage is 96.29%.

@@                  Coverage Diff                  @@
##             postgresql-dialect     #279   +/-   ##
=====================================================
  Coverage                 82.29%   82.29%           
- Complexity                 1277     1278    +1     
=====================================================
  Files                       102      102           
  Lines                      4410     4411    +1     
  Branches                    548      546    -2     
=====================================================
+ Hits                       3629     3630    +1     
  Misses                      598      598           
  Partials                    183      183           

Flag	Coverage Δ
all_tests	82.29% <96.29%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
...pter/statements/IntermediatePreparedStatement.java	84.26% <95.45%> (-0.27%)	⬇️
.../pgadapter/metadata/DescribeStatementMetadata.java	100.00% <100.00%> (ø)
...panner/pgadapter/wireprotocol/DescribeMessage.java	84.37% <100.00%> (+0.24%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fe56a53...01f1563. Read the comment docs.