Support for temporary credential with OIDC

## This should be in gist but no other place to put it.
This action supports the use of OIDC for authentication

## Instead of the AWS Access KEY, which inherits human flaws and cannot be whitelisted

```
uses: appleboy/lambda-action@v0.2.0
with:
aws_access_key_id: ${{ secrets.AWS_ACCESS_KEY_ID }}
aws_secret_access_key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
aws_region: ${{ secrets.AWS_REGION }}
function_name: gorush
zip_file: output.zip
dry_run: true
```

## With OIDC/AUTH2, granular permissions can be given with temporary access.
The example below shows the action used with OIDC support.

- name: Configure AWS credentials
uses: aws-actions/configure-aws-credentials@v4
with:
role-to-assume: arn:aws:iam::${{ secrets.awsAccountId }}:role/github-actions-oidc-role
aws-region: ${{ secrets.AWS_REGION }}

- name: Deploy function
uses: appleboy/lambda-action@v0.2.0
with:
function_name: function_name
zip_file: funciton.zip
aws_region: region_name

まず issue のサンプル workflow を読み、既存の AWS access-key inputs と aws-actions/configure-aws-credentials@v4 step を比較します。この action がどのように credentials を受け取るのか、また OIDC ベースの使用方法がどのようになるべきかを確認します。完了条件は、一時的な role で static access-key inputs を使わずに Lambda を deploy でき、ドキュメントまたは workflow validation でこの例がカバーされていることです。

索引モデルが issue の本文から書いたものです。