Extend test coverage for S3 streaming upload

[losipiuk]

Extra testing

#10710 showed that we are lacking test coverage for S3 streaming upload.
We should write testcases which upload files of multiple sizes with S3 streaming enabled (default currently). Specifically

• file of size less than 16MB (multipart size)
• file of size greater than 16MB but less than 32MB (it was a trigger for Support writing timestamp(0) as datetime type in ClickHouse #10751
• file of size greater thatn 32MB

For tests which talk to real S3 endpoint on AWS we should extend AbstractTestHiveFileSystemS3 (this test is run for master and for PRs originated from trinodb/trino).

AbstractTestHiveFileSystemS3 is a low-level test in which we directly create PageSink etc. To have more blackbox coverage we can also write an integration test which uses MiniIO based QueryRunner and consumes SQL statements to trigger writing.
For that BaseTestHiveOnDataLake can be extended.

Extra guards in TrinoS3FileSystem

Additionally it would be nice to add extra guards to TrinoS3FileSystem filesystem which ensure that close() would not call finishUpload if file upload is alredy considered completed; when code path which uploads small files without multipart mechanism
is executed. Having such guard would prevent #10710 from happening.

cc: @linzebing @findepi @joshthoward

[losipiuk]

Reopened because added test proved to be flaky and was disabled.

[linzebing]

Closed via #11678