[Pg] AWS Data API fixes

[hugo082]

This PR address multiple issues on AWS Data API driver, each via a separate commit.

1. Reconciliation of AwsDataApiSession with PgSession base class

The third parameter of AwsDataApiSession.prepareQuery should be the name to stay compatible with the postgres query builder especially the .prepare(name: string) method. - #1171

• The transactionId is now the fifth one. Anyway it is used internally only. Note that it is also possible to remove the parameter as we have the value on the session instance properties.
• the name parameter is ignored (as on neon-http driver & some others)

2. Fix the transaction id propagation

If the transaction id is not provided on the query, the session should use the current one, the one stored on the instance.

3. Fix nested transactions

• await for the savepoint to be created / rollback / released before continuing
• await for the transaction handler to be executed for releasing the savepoint
• do not use parameters on savepoints queries as it is not supported by AWS Data API - [BUG]: AWS Data API nested transactions - savepoints #1936

4. Tests fixes

Fix outdated tests (mainly because the returned values doesn't match the type on raw execution).

We probably should update the AwsDataApiPgQueryResultHKT.type: aws.ExecuteStatementCommandOutput but i'm not sure what would be the right value. Probably something similar to the neon-serverless version NeonQueryResultHKT.type: QueryResult<Assume<this['row'], QueryResultRow>>;

[hugo082]

AWS Data API tests suite

Before	After

[jakeleventhal]

You should check out these PRs as well:
#1933
#1931
#1911

[hugo082]

Hi @dankochetov @AndriiSherman 👋

What are the next steps to merge these fixes? Do you think there is any change to merge them during the month?

[dankochetov]

@hugo082 please sign your commits
https://docs.github.com/articles/about-gpg/

[hugo082]

@hugo082 please sign your commits docs.github.com/articles/about-gpg

@dankochetov done ✅

[hugo082]

@dankochetov, any updates?

[dankochetov]

@hugo082 yes, I'm testing it myself and making adjustments, hoping to merge in the next few days

[dankochetov]

I've pushed this PR with my changes into a separate branch, will continue it in #2119