chore(deps): use aws-sdk-go-v2

[MaineK00n]

What did you implement:

https://aws.github.io/aws-sdk-go-v2/docs/migrating/

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

vuls report -to-s3

envvar

$ AWS_ACCESS_KEY_ID=<AWS_ACCESS_KEY_ID> AWS_SECRET_ACCESS_KEY=<AWS_SECRET_ACCESS_KEY> vuls report -to-s3

credential files

$ cat ~/.aws/credentials

$ vuls report -to-s3

EC2 IMDS

$ curl 169.254.169.254/latest/meta-data/instance-id/

$ vuls report -to-s3

vuls saas

$ vuls saas

Checklist:

You don't have to satisfy all of the following.

• Write tests
• Write documentation
• Check that there aren't other open pull requests for the same issue/feature
• Format your source code by make fmt
• Pass the test by make test
• Provide verification config / commands
• Enable "Allow edits from maintainers" for this PR
• Update the messages below

Is this ready for review?: YES

Reference

[MaineK00n]

https://github.com/aws/aws-sdk-go-v2/blob/728f21ff766e27bf28e6f30c0c1508c4cb7b2ed5/config/config.go#L199

https://github.com/aws/aws-sdk-go-v2/blob/728f21ff766e27bf28e6f30c0c1508c4cb7b2ed5/config/config.go#L67

https://github.com/aws/aws-sdk-go-v2/blob/728f21ff766e27bf28e6f30c0c1508c4cb7b2ed5/config/resolve_credentials.go#L58-L183

[shino]

Perfect!

[shino]

Behavior changed slightly.

When "profile" is specified in config.toml and "AWS_ACCESS_KEY_ID" and "AWS_SECRET_ACCESS_KEY" are specified in environment variables,

Before: "AWS_ACCESS_KEY_ID" and "AWS_SECRET_ACCESS_KEY" are used
After: "profile" in config.toml is used

For someone who is running vuls in such configurations, please watch out.