Add uri flag for s3 path style addressing configuration

[EdwardDowling]

Add ability to disable path-style S3 access for third-party endpoints.

part of: #48451
Fixes https://github.com/gravitational/customer-sensitive-requests/issues/346

changelog: Add ability to disable path-style S3 access for third-party endpoints.

[programmerq]

This change looks good to me, but should probably have the storage backend doc reflect the change: https://github.com/gravitational/teleport/blob/master/docs/pages/reference/backends.mdx#s3-session-recordings

I think we'd only need to add this bullet point underneath the endpoint description.

• use_s3_path_style - Whether to use path-style instead of virtual-host-style URLs for the bucket. Only applies when a custom endpoint is set. Defaults to true when unset. If used without a custom endpoint set, this option has no effect.

I'm happy to add this doc commit to the branch for this PR if it's helpful.

[EdwardDowling]

This change looks good to me, but should probably have the storage backend doc reflect the change: https://github.com/gravitational/teleport/blob/master/docs/pages/reference/backends.mdx#s3-session-recordings

I think we'd only need to add this bullet point underneath the endpoint description.

* `use_s3_path_style` - Whether to use path-style instead of virtual-host-style URLs for the bucket. Only applies when a custom `endpoint` is set. Defaults to `true` when unset. If used without a custom `endpoint` set, this option has no effect.

I'm happy to add this doc commit to the branch for this PR if it's helpful.

Added it in there

[github-actions]

Amplify deployment status

Branch	Commit	Job ID	Status	Preview	Updated (UTC)
edwarddowling/path-style	5c5cd76	6	✅SUCCEED	edwarddowling-path-style	2025-02-10 16:09:47

[EdwardDowling]

@hugoShaka @tcsc Can you take a look at this when you get a chance

[hugoShaka]

Can we do a real-world test against an s3 backend not supporting path-style adressing and see if we can make teleport work? Or maybe send a dev build to the affected customer?

[r0mant]

lgtm after you fix the docs

[r0mant]

Please make sure to retest everything again since we've inverted the flag here and if everything is ok let's ship it.

[EdwardDowling]

Confirmation that the dev build worked for the customer here

[public-teleport-github-review-bot]

@EdwardDowling See the table below for backport results.

Branch	Result
branch/v15	Failed
branch/v17	Create PR