python s3transfer and boto3 versioning conflicts after commit 118a3b5

[ericmeyers12-arthrex]

When trying to do a pip install on boto3==1.39.13 and s3transfer==0.14.0 locally (the same versions of the respective recipes in this layer on the scarthgap branch), I see the following:

ERROR: Cannot install boto3==1.39.13 and s3transfer==0.14.0 because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested s3transfer==0.14.0
    boto3 1.39.13 depends on s3transfer<0.14.0 and >=0.13.0

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

(just showing this as an example of what initially prompted this issue submission)

On the scarthgap branch, the python3-s3transfer recipe was upgraded from 0.13.1 -> 0.14.0 in this commit: 118a3b5

However, the python3-boto3 recipe (still in scarthgap) is still set to version 1.39.13. Looking at setup.py in the boto3 repo (here), v1.39.13 requires a s3transfer version strictly less than 0.14.0.

So that makes me think either:

1. python3-s3transfer should not have been version bumped on scarthgap from 0.13.1 -> 0.14.0, OR
2. python3-boto3 should be bumped in lockstep to version 1.40.41 (or a compatible version) to match what master has.

Are these assumptions correct, or is there something I'm missing?