Example AWS IAM profile in Object Storage docs appears to be incorrect

While building out an example AWS Reference Architecture environment I noticed we had an example AWS IAM profile in the docs to grant Object Storage access to the VMs.

Switching to this profile resulted in errors however, specifically when attempting to import a project:

    - Expected(200) \u003c=\u003e Actual(403 Forbidden)\nexcon.error.response\n  :body          =\u003e \"\"\n  :cookies       =\u003e [\n  ]\n  :headers       =\u003e {\n    \"Content-Type\"      =\u003e [FILTERED]\n    \"Date\"              =\u003e \"Tue, 08 Dec 2020 13:06:11 GMT\"\n    \"Server\"            =\u003e \"AmazonS3\"\n    \"Transfer-Encoding\" =\u003e \"chunked\"\n    \"x-amz-id-2\"        =\u003e [FILTERED]\n    \"x-amz-request-id\"  =\u003e \"243BEAC22EE971C5\"\n  }\n  :host          =\u003e \"gitlab-qa-10k-test-object-storage.s3.amazonaws.com\"\n  :local_address =\u003e \"172.31.67.222\"\n  :local_port    =\u003e 58088\n  :path          =\u003e [FILTERED]\n  :port          =\u003e 443\n  :reason_phrase =\u003e \"Forbidden\"\n  :remote_ip     =\u003e \"52.217.12.92\"\n  :status        =\u003e 403\n  :status_line   =\u003e [FILTERED] 403 Forbidden\\r\\n\"\n","error_class":"RuntimeError","db_duration_s":0.039396}'

Unfortunately the above error doesn't call out what specific s3 action permission(s) is missing for the example.

We should figure out what all s3 actions GitLab will try to use and update this above docs accordingly.