Clarify s3 bucket configurations for registry usage

What does this MR do?

A customer or user may accidentally configure their s3 storage in a way that causes s3-backed features to break. I saw this in Support recently: https://gitlab.zendesk.com/agent/tickets/145320. In this ticket, the customer added a lifecycle to the s3 bucket being used for their registry. When some items were aged into unsupported storage it caused their pipelines to start breaking, which took many hours to resolve.

This updates the verbiage for supported s3 bucket configurations for registry usage.

-->

Screenshots

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

This is a doc update to prevent misconfiguration.

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team