AWS Go SDK V2 Upgrade, Single Measure Support

[fredjoonpark]

This PR upgrades the AWS go SDK used for connecting to Timestream. Added mode for toggling between single-measure and multi-measure records, including for query generation with relevant tests.

To run unit tests for generated queries, you can navigate to cmd/tsbs_generate_queries/databases/timestream and run go test -v.

Sample end-to-end flow:

1. Generate data

tsbs_generate_data --use-case="cpu-only" --seed=123 --scale=10 \
    --timestamp-start="2025-02-17T00:00:00Z" \
    --timestamp-end="2025-02-18T00:00:00Z" \
    --log-interval="10s" --format="timestream" \
    | gzip > /tmp/timestream-data.gz

And unzip with gunzip /tmp/timestream-data.gz

2. Generate queries

Multi-measure:

tsbs_generate_queries --use-case="cpu-only" --seed=123 --scale=10 \
    --timestamp-start="2025-02-17T00:00:00Z" \
    --timestamp-end="2025-02-18T00:00:01Z" \
    --queries=3 --query-type="high-cpu-1" --format="timestream" \
    | gzip > /tmp/timestream-queries.gz

Single-measure:

tsbs_generate_queries --use-case="cpu-only" --seed=123 --scale=10 \
    --timestamp-start="2025-02-17T00:00:00Z" \
    --timestamp-end="2025-02-18T00:00:01Z" \
    --queries=3 --query-type="high-cpu-1" --format="timestream" --timestream-use-single-measure="true" \
    | gzip > /tmp/timestream-queries.gz

3. Generate config

Create the config with:

tsbs_load config --target=timestream --data-source=FILE

And update config values:

• Update data source location (/tmp/timestream-data)
• If using single-measure records, set use-single-measure-records to true
• Increase workers (really slow with just 1)

4. Load data

./bin/tsbs_load load timestream --config=./config.yaml

5. Run queries

cat /tmp/timestream-queries.gz | \
    gunzip | tsbs_run_queries_timestream --workers=8

Run with --print-responses to track progress of your queries.

[forestmvey]

Looks good after comments have been addressed

[fredjoonpark]

Created a PR against this branch for addressing all of the comments. Updating seed triggered a pretty broad change, verified tests related to the core changes are passing and created a separate ticket for updating the tests in the InfluxDB module.