S3 gateway only looks at HTTP verb, not at full S3 action

[arielshaqed]

Followup from #6930. What really happens there is that the gateway assumes only a very narrow set of S3 actions will be used, and ends up performing almost only object CRUDs.

For instance, I can call the list-object-versions API:

❯ aws s3api  list-object-versions --bucket ariels-repo  --prefix main
{
    "CommonPrefixes": [
        {
            "Prefix": "main/"
        }
    ],
    "RequestCharged": null
}

It performs exactly list-objects:

❯ aws s3api  list-objects-v2 --bucket ariels-repo  --prefix main
{
    "CommonPrefixes": [
        {
            "Prefix": "main/"
        }
    ],
    "RequestCharged": null
}

But of course lakeFS does not support S3-style object versions, and s3://ariels-repo/main is not an object on lakeFS, and it certainly does not have any versions, and this response does not follow the response syntax for this action.

[arielshaqed]

Context from original issue: this comment