Add S3 addressing style configuration support

[ranjit-parva]

• Add adressing_style field to S3Config
• Add S3_ADDRESSING_STYLE config entry with support for legacy and YAML config
• Configure S3 client to use virtual addressing style when specified

Related PR:
flyteorg/stow#20

[welcome]

Thank you for opening this pull request! 🙌

These tips will help get your PR across the finish line:

• Most of the repos have a PR template; if not, fill it out to the best of your knowledge.
• Sign off your commits (Reference: DCO Guide).

[kumare3]

Why do you need addressing style? The yaml config entry will break flytectl in struct mode as that config is not there

[davidmirror-ops]

@ranjit-parva thanks for your contribution.
Could you elaborate on what problem this solves? I'm struggling a bit to understand why this is needed

[ranjit-parva]

@ranjit-parva thanks for your contribution. Could you elaborate on what problem this solves? I'm struggling a bit to understand why this is needed

Virtual Host-style and Path-style addressing differ in how the bucket name is positioned within the URL, either as a subdomain or as part of the path. Virtual Host-style (e.g., https://bucket.s3.amazonaws.com) is the current AWS standard and is required for all buckets created after September 2020 to ensure better traffic routing and scalability. Path-style (e.g., https://s3.amazonaws.com/bucket) is considered legacy but remains widely used in local development environments like LocalStack or MinIO for easier DNS configuration.

By default path sytle is picked by boto. This config enables users to set virtual host style.

[welcome]

Congrats on merging your first pull request! 🎉