feat: redshift data driver

[atzoum]

Description

Including the option to use an alternative sql driver for redshift, based on the Redshift Data API Service.

Credentials example for using the new redshift-data driver:

{
    "type": "redshift-data", <-- type qualifier
    "clusterIdentifier": "clusterIdentifier",
    "database": "database",
    "user": "user",
    "region": "region",
    "sharedConfigProfile": "sharedConfigProfile"
}

Credentials example for using the original postgres driver:

{
    "host": "host",
    "port": 5432,
    "dbname": "dbname",
    "user": "user",
    "password": "password",
    "sslmode": "sslmode"
}

The sqlconnect.DB interface's behaviour remains the same regardless which driver is being used, in terms of:

• Column mappings
• Json mappings
• SQL dialect support & parameterized queries

However, differences shall be expected by clients in the following:

• Prepared statements: the driver doesn't actually prepare any statement against the data API, it merely caches it in memory, until the caller decides to execute it.
• Transactions: the Data API doesn't support transactions natively, it only supports batch execution of statements. Driver's transactions are implemented on top of the batch execution API, therefore only ExecContext operations are allowed in the context of an ongoing transaction, not QueryContext.

Security

• The code changed/added as part of this pull request won't create any security issues with how the software is being used.

[atzoum]

Note: redshift-data driver returns some imprecise value, e.g. 1.10000000034

[atzoum]

Note: redshift-data driver returns some imprecise value, e.g. 1.10000000034

[atzoum]

Note: redshift-data driver returns NUMERIC data types as string instead of []byte

[codecov]

Codecov Report

Attention: Patch coverage is 75.22124% with 140 lines in your changes are missing coverage. Please review.

Project coverage is 85.84%. Comparing base (87f2a09) to head (92b401f).

Files	Patch %	Lines
sqlconnect/internal/redshift/driver/connection.go	64.97%	48 Missing and 28 partials ⚠️
sqlconnect/internal/redshift/driver/dsn.go	84.56%	13 Missing and 10 partials ⚠️
sqlconnect/internal/redshift/driver/rows.go	74.24%	11 Missing and 6 partials ⚠️
sqlconnect/internal/redshift/config.go	60.00%	2 Missing and 2 partials ⚠️
sqlconnect/internal/redshift/driver/driver.go	73.33%	2 Missing and 2 partials ⚠️
sqlconnect/internal/redshift/driver/result.go	77.77%	2 Missing and 2 partials ⚠️
sqlconnect/internal/redshift/driver/statement.go	66.66%	4 Missing ⚠️
sqlconnect/internal/redshift/db.go	95.12%	1 Missing and 1 partial ⚠️
sqlconnect/internal/redshift/driver/client.go	66.66%	1 Missing and 1 partial ⚠️
sqlconnect/internal/redshift/driver/connector.go	81.81%	1 Missing and 1 partial ⚠️
... and 1 more

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #18      +/-   ##
==========================================
- Coverage   88.33%   85.84%   -2.50%     
==========================================
  Files          59       70      +11     
  Lines        2143     2684     +541     
==========================================
+ Hits         1893     2304     +411     
- Misses        173      251      +78     
- Partials       77      129      +52     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[atzoum]

Note: to be compatible with the behaviour of pg driver, we need to:

• Parse the string into a time
• Convert the time to UTC and parse it as an RFC3339 string.