Drop AWS SDK for Go v1 and upgrade to v2 before EOL/end-of-support at July 31, 2025

### What would you like?

### Requirement

As far as I can see there is an indirect dependency for `github.com/aws/aws-sdk-go` (AWS SDK for Go **v1**) in Go kit:
https://github.com/go-kit/kit/blob/78fbbceece7bbcf073bee814a7772f4397ea756c/go.mod#L8

### Problem

According to this https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-sdk-for-go-v1-on-july-31-2025/,
there will be no more releases for AWS SDK for Go v1 after July 2025. AWS as maintainer of this AWS SDK for Go package announced the **EOL of the version 1 for July 31, 2025**. After this date, there are **no** critical bug fixes and **no** security issues provided.

### Proposal

Go kit should consider migrating (or updating references modules) to [AWS SDK for Go v2](https://aws.github.io/aws-sdk-go-v2/docs/) - https://github.com/aws/aws-sdk-go-v2/ to reduce the technical dept and converges to use a single version of this SDK: `github.com/aws/aws-sdk-go-v2` (I can also see already usage of v2 in Go kit).

I found the following PRs / notes:

>_Originally posted by @sagikazarmark in [#1109](https://github.com/go-kit/kit/issues/1109#issuecomment-864390125)_
> We should consider upgrading to the v2 SDK for AWS. It's not a giant module anymore for every service.

> _Originally posted by @sagikazarmark in [#1109](https://github.com/go-kit/kit/issues/1109#issuecomment-865662414)_
> PRs sent. I left the "old" AWS SDK in place for now. I couldn't tell the difference between cloudwatch and cloudwatch2. If the only difference is the AWS SDK version, we could just deprecate the old one.

Maybe there is a chance to drop the `github.com/aws/aws-sdk-go` reference from Go kit within an upcoming release/PR? - Maybe it is an "old relic"?