Some clients (WinSCP, android mp3 player) do not work correctly

A user has reported this:

> trying to use other apps like android s3 music player won't work because it tries to "list buckets" within the single bucket connection =(
context:
if I connect to the store without specifying a /bucket-name string after the subdomain.domain I get an error saying "Specify Target Bucket" at the WinSCP client (when trying to upload something)
at the same time there's no list of available buckets (even the 1 created with bucketClaim+bucketAccess combo)
so I rather connect using /bucket-name at the url (using folders settings in WinSCP) or the connection is credential-valid but not usable
finally more basic apps like the android mp3 player for s3 buckets will throw an error because it will stay in the same situation: trying to list buckets

This is the default set of allowed policy actions, which don't seem to be allowing clients to list their own buckets despite the `ListAllMyBuckets` permission being set:
https://github.com/ceph/ceph-cosi/blob/fed3305df395e4a3d65c2d34426b220ce43f2fe4/pkg/util/s3client/policy.go#L79-L112

It's unclear to me exactly what the issue is. This could be a permissions issue from COSI, or perhaps these clients require vhost-style access. We are working on that in Rook here: https://github.com/rook/rook/pull/13022

Start with pkg/util/s3client/policy.go at lines 79-112 and inspect the default policy actions, then review the reported WinSCP and Android client behavior. Compare this with the Rook PR 13022 context to determine whether the failure is caused by permissions or vhost-style access; done means establishing the cause and a client-compatible resolution.

Written by the indexing model from the issue text.