Concurrent uploading results in WrongRequestBodyStreamSize

[lehins]

Update to new version of stackage lts (thus all dependencies) resulted in concurrent uploading producing an error

[cache-s3][Info ][Sat, 14 Sep 2019 17:32:38 UTC]: <cache-s3/fpco/cache-s3/master.windows.lts-14.4.stack-work.cache> - Data change detected, caching 41.7 MiB with sha256: g1kXWt1frFHU7VM/9hvo0hjIAlJM7y4VtquJlJA6tYc=
[cache-s3][Warn ][Sat, 14 Sep 2019 17:32:40 UTC]: <cache-s3/fpco/cache-s3/master.windows.lts-14.4.stack-work.cache> - TransportError - WrongRequestBodyStreamSize 43626199 8388608

The issue has been reported upstream in axman6/amazonka-s3-streaming#17 as well as brendanhay/amazonka#548 so if anyone is willing to tackle it, feel free to do so, but until then, cache-s3 will be doing uploading sequentially from v0.1.10 until better times.

This feature was originally implemented in #20 so
CC @aledeganopix4d @wagdav, @mbj and @rvl

[domenkozar]

Hopefully once axman6/amazonka-s3-streaming#22 is merged, you can use it instead of concurrentUpload.