feat: credentials sort (#2)

### TL;DR

Reordered AWS credential providers and removed domain regex filtering for CodeArtifact repositories.

### What changed?

- Bumped `releaseVersion` from `0.0.3` to `0.0.4`
- Reordered AWS credential providers in `getAwsCredentials()` function, moving `ProfileCredentialsProvider` after `ContainerCredentialsProvider` and `InstanceProfileCredentialsProvider`
- Removed the domain regex filtering logic in the `isCodeArtifactRepository()` function, so all valid CodeArtifact endpoints are now recognized without additional filtering

### How to test?

1. Verify that AWS credential resolution works correctly in different environments
2. Confirm that all CodeArtifact repositories are properly recognized without needing to set the `codeartifact.domains` system variable

### Why make this change?

The credential provider reordering improves the AWS authentication flow by prioritizing container and instance profile credentials before profile credentials. Removing the domain regex filtering simplifies the repository recognition logic, eliminating the need for additional configuration through system variables.

Add release workflow and update AWS credentials provider chain (#1)

### TL;DR

Added GitHub release automation workflow and updated AWS credential provider chain.

### What changed?

- Added release automation with GitHub Actions:
  - Created `.github/release-drafter-config.yml` to define release notes format with Korean category labels
  - Added `.github/workflows/release.yml` to automate plugin publishing when release tags are pushed
- Updated AWS credential provider chain in `Credentials.kt` to include:
  - Added `WebIdentityTokenFileCredentialsProvider` as first priority
  - Added `EnvironmentVariableCredentialsProvider` as second priority
  - Reordered credential providers for better precedence
- Bumped version from 0.0.2 to 0.0.3 in `gradle.properties`

### How to test?

1. Push a tag with format `release/*` to trigger the release workflow
2. Verify the release draft is created with proper categorization
3. Test AWS credential resolution in different environments to ensure proper provider precedence

### Why make this change?

- Streamlines the release process with automated changelog generation and plugin publishing
- Improves AWS credential resolution by adding support for web identity tokens and environment variables
- Enhances security by prioritizing more secure credential providers in the chain

feat: aws credentails chains, profile, default, container, instance p…

…rofile

fix: warn tags remove