HDDS-12359. Bump async profiler to 2.9, awscli to 1.37

[adoroszlai]

What changes were proposed in this pull request?

Bump dependencies:

• async profiler 2.9
• awscli 1.37 (latest version)

https://issues.apache.org/jira/browse/HDDS-12359

How was this patch tested?

#20 7.998 Successfully installed PyYAML-6.0.2 awscli-1.37.21 boto3-1.36.21 botocore-1.36.21 colorama-0.4.6 docutils-0.16 jmespath-1.0.1 pyasn1-0.6.1 python-dateutil-2.9.0.post0 robotframework-6.1.1 rsa-4.7.2 s3transfer-0.11.2 six-1.17.0 urllib3-1.26.20
...
#23 0.390 + mv async-profiler-2.9-linux-x64 /opt/profiler

https://github.com/adoroszlai/ozone-docker-runner/actions/runs/13377374876/job/37359340791#step:7:1137

[jojochuang]

This change doesn't break robot tests due to HDDS-12123 because we run S3G in HTTP not HTTPS mode.

async profiler 2.9 is backward compatible. Moving to 3.0 and beyond requires change similar to this one https://github.com/apache/hbase/pull/6625/files

[adoroszlai]

Thanks @jojochuang for the review. My main goal is to create an image that allows testing with the latest awscli.

[ivandika3]

Hi @adoroszlai , I didn't see the awscli upgrade in this patch. Is it implicitly upgraded somehow?

[adoroszlai]

I didn't see the awscli upgrade in this patch. Is it implicitly upgraded somehow?

Yes, pip installs the latest one.

[ivandika3]

Yes, pip installs the latest one.

I see, this means that the AWS CLI version depends on when the pip install is run (I guess when the docker image is build).

IMO, I prefer if we can make it explicit so that we can know exactly which AWS CLI version is used. However, we can let this be for now.

[adoroszlai]

IMO, I prefer if we can make it explicit so that we can know exactly which AWS CLI version is used.

I agree, we use the same method for Robot Framework and few other tools included in the image. Created HDDS-12499.