Remove direct aws sdk dependencies

[matwojcik]

I suggest not adding AWS SDK dependencies directly, but depend on those that come from pure-xxx-tagless. The reason behind is the fact, that mostly this is pure-xxx-tagless which uses that SDK directly. Bumping that AWS SDK version on our own in pass4s can lead to unpredictable behaviour, like runtime errors because of backward incompatible AWS SDK changes.

For example in 2.21.7 there was a breaking change in AWS SDK - a QueryParametersToBodyInterceptor was moved to another package aws/aws-sdk-java-v2@04dffd7. In case of pure-xxx-tagless dependends on 2.20.x and pass4s on 2.21.7 then we would have runtime errors.

[bwiercinski]

aren't unit and integration tests which are implemented in this project sufficient to check that the class is missing? i think this kind of failures can be detected by the simplest smoke tests

[bwiercinski]

these overrides were added because pure-xxx-tagless doesn't have often an update. and often aws skd have some vulnerabilities found. of course a client of the pass4s can override the aws sdk by himself/herself, but then he wouldn't run the mentioned tests which are implemented in pass4s project

[matwojcik]

these overrides were added because pure-xxx-tagless doesn't have often an update. and often aws skd have some vulnerabilities found. of course a client of the pass4s can override the aws sdk by himself/herself, but then he wouldn't run the mentioned tests which are implemented in pass4s project

Exactly this is the case. Apart from that, it can happen that not all the paths are covered in the tests, and main user of the SDK (so tagless lib) breaks then.

[matwojcik]

I've asked for release laserdisc-io/fs2-aws#1122, however the previous ones were not that far away, so hopefully that should not be that problematic in the future.