refactor: upgrade aws-sdk-go to v2 for s3 storage

[cshum]

No description provided.

[chladog]

The latest version 1.5.12 broke our S3-connected imagor resulting in unaccessible images with message {"message":"http source not allowed","status":403}
Do we need to reconfigure it somehow? Version 1.5.11 is working normally

We use

            - name: S3_FORCE_PATH_STYLE
              value: '1'

[cshum]

@chladog Thanks for reporting this issue. I'm investigating it at #588 .

To help me understand the problem, could you please provide a bit more information?

• Are you using a custom S3 endpoint (like MinIO or Cloudflare R2)?
• Would you be able to share the other Imagor configuration options you have set (excluding any secret credentials)?
• If possible, a reproducable docker-compose.yml configuration would be extremely helpful.