Upgrade AWS SDK for Go from V1 to V2

[snaka]

Overview

This Pull Request aims to upgrade the version of the AWS SDK for Go from V1 to V2.

Changes

• Updated the AWS SDK for Go dependency from V1 to V2.
• Refactored relevant code to be compatible with the V2 SDK changes.
• Fixed any deprecated methods and ensured the application's functionality remains consistent.

Main changes from V1 to V2

• Method to create Service Client instances
  • https://aws.github.io/aws-sdk-go-v2/docs/migrating/#client-construction
• The <OperationName>WithContext method for calling APIs has been renamed to just <OperationName>
  • https://aws.github.io/aws-sdk-go-v2/docs/migrating/#invoking-api-operations
• Service Data Types are now defined under the types package for each service
  • https://aws.github.io/aws-sdk-go-v2/docs/migrating/#service-data-types
• aws.StringValue() has been changed to aws.ToString()
  • https://aws.github.io/aws-sdk-go-v2/docs/migrating/#pointer-parameters

Changes Made with Uncertainty

• I'm not confident that replacing session.NewSessionWithOptions() with config.LoadDefaultConfig() maintains equivalent behavior to the original. ( However, as far as I have confirmed, it seems to work the same way, so there may not be a problem.)
  • Based on the SDK V1 documentation, it seemed the original intention was to read the Shared config (~/.aws/*) by specifying session.SharedConfigEnable.
    • session - Amazon Web Services - Go SDK
  • In the SDK V2 documentation, it states that config.LoadDefaultConfig() reads the shared config, so I have replaced it with this function.
    • Configuring the AWS SDK for Go V2 | AWS SDK for Go V2

Testing

The following has been tested

• Unit test succeeded.
• Verified that the subcommands apply, dump, run, and diff can be executed.

Behavior Incompatibility

• dump now always includes the propagateTag when retrieving remote Rule information.
  • This means that propagateTag: "" will be output as a diff if propagateTag is not explicitly specified in config.yaml.
  • This behavior has the same result when displaying differences with apply or diff.
  • To solve this problem, it is necessary to change the way config default values are handled, which is out of the scope of this PR. ( I think it would be better to address this in a another PR).

[Songmu]

Thank you. Released as v0.11.0.