testS3Connection missing other checks

Video in comments.

I was able to trace down to "s3:ListBucket" not being checked by testS3Connection utility. meaning without "s3:ListBucket" permission testS3Connection can say everything is ok but a problem still exists when starting up columnstore via the debug.log you see

S3Storage::exists(): failed to HEAD, got 'Authentication failed'.

Expected:
When using testS3Connection and it says OK. that the cluster can startup fine and store data in S3.

Actual:
Not having s3:ListBucket, you cant use S3 storage for columnstore

Minimum S3 permission needed for access key/secret S3 auth determined:

                "s3:PutObject",

                "s3:PutObjectAcl",

                "s3:GetObject",

                "s3:GetObjectAcl",

                "s3:DeleteObject",

                "s3:ListBucket"