Adding python boto3 task

[arunvel1988]

Changes

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you review them:

• [ ] Follows the authoring recommendations
• [ ] Includes docs (if user facing)
• [ ] Includes tests (for new tasks or changed functionality)
  • See the end-to-end testing documentation for guidance and CI details.
• [ ] Meets the Tekton contributor standards (including functionality, content, code)
• [ ] Commit messages follow commit message best practices
• [ ] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep

• [ ] Complies with Catalog Organization TEP, see example. Note An issue has been filed to automate this validation

  • [ ] File path follows <kind>/<name>/<version>/name.yaml
  • [ ] Has README.md at <kind>/<name>/<version>/README.md
  • [ ] Has mandatory metadata.labels - app.kubernetes.io/version the same as the <version> of the resource
  • [ ] Has mandatory metadata.annotations tekton.dev/pipelines.minVersion

  • [ ] mandatory spec.description follows the convention

    
      spec:
        description: >-
          one line summary of the resource
    
          Paragraph(s) to describe the resource.

See the contribution guide for more details.

[linux-foundation-easycla[bot]]

• :white_check_mark:login: arunvel1988 / (29a7a57e16148fcfd049aa2ab93a0eb92f9efeb3)
• :x: login: @arunvelarunachalam / The commit (2a15a3df14bf233206858a3716d7a1f9dbda4828, 6174a75d808164921d31162ba6b2459f46eadfdb). This user is authorized, but they must confirm their affiliation with their company. Start the authorization process by clicking here, click \"Corporate\", select the appropriate company from the list, then confirm your affiliation on the page that appears. For further assistance with EasyCLA, please submit a support request ticket.

[tekton-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: To complete the pull request process, please assign vdemeester after the PR has been reviewed. You can assign the PR to them by writing /assign @vdemeester in a comment when ready.

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

Needs approval from an approver in each of these files: - **[OWNERS](https://github.com/tektoncd/catalog/blob/main/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[tekton-robot]

Hi @arunvel1988. Thanks for your PR.

I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[arunvel1988]

cla issue

[tekton-robot]

Catlin Output

``` FILE: task/python-boto3-aws/0.1/python-boto3-aws.yaml ERROR: Resource path is invalid; expected path: task/python-boto3/0.1/python-boto3.yaml ERROR: Category not defined You can choose from the categories present at location: https://raw.githubusercontent.com/tektoncd/hub/main/config.yaml" ERROR: Task: tekton.dev/v1beta1 - name: "python-boto3" must have a description WARN : Step "run-python-script" uses image "python:3.9"; consider using a fully qualified name - e.g. docker.io/library/ubuntu:1.0 WARN : Step "run-python-script" uses secret to populate env "AWS_ACCESS_KEY_ID". Prefer using secrets as files over secrets as environment variables WARN : Step "run-python-script" uses secret to populate env "AWS_SECRET_ACCESS_KEY". Prefer using secrets as files over secrets as environment variables ```

[arunvel1988]

@vinamra28 kindly review this PR