feat(apps/prod/tekton/configs): use aws-cli to upload to qiniu

[wuhuizuo]

prepare for compatible with future object storage providers.

Signed-off-by: wuhuizuo wuhuizuo@126.com

[ti-chi-bot]

I have already done a preliminary review for you, and I hope to help you do a better job.

The Pull Request (PR) is titled "feat(apps/prod/tekton/configs): use aws-cli to upload to qiniu". It aims to update the configuration files in the Tekton CI/CD pipeline to use AWS CLI for uploading files to the Qiniu cloud storage.

Key changes in the PR:

1. The Qiniu credentials parameter (qiniu-creds-secret-name) is removed and replaced with AWS credentials (aws-secrets-tencent).
2. The AWS secrets are added as optional workspaces in multiple tasks within the pipeline.
3. The build image tag has been updated in multiple files from v20240325-60-gb6f8928 to v2024.10.8-71-gf13e219.
4. The code for uploading files to Qiniu is replaced with AWS CLI commands for uploading files to S3.
5. The indentation of some lines of code has been adjusted to maintain consistency.

Potential problems:

1. No information is provided whether the AWS CLI is installed or not in the environment where this pipeline will run.
2. The AWS secrets and bucket name are expected to be found in the workspace, but there is no check or handling if they are not provided or incorrect.
3. Directly changing the storage provider from Qiniu to S3 might lead to potential compatibility issues, like different file paths, API behaviors, etc.
4. The PR doesn't include any tests to verify whether the changes work as expected.

Suggestions to fix:

1. Make sure the AWS CLI is installed in the environment where this pipeline runs.
2. Add error handling for cases where the AWS secrets or bucket name are not provided or incorrect.
3. Conduct a thorough analysis to understand the impact of changing the storage provider to avoid any potential issues.
4. Include tests in the PR to verify that the changes work as expected.
5. It would be better to provide more details in the PR description about why this change needs to be made, how it was tested, and any potential impact this change may cause to existing systems or processes.

[wuhuizuo]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wuhuizuo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• apps/prod/OWNERS [wuhuizuo]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment