chore: add requirements.in files with fixed versions to use in pip

[echyam]

/kind cleanup

Is this a bug fix or adding new feature?
Makes pip install install fixed versions with a xxx-requirements.in file per package (aws, yamale, yamllint)

What is this PR about? / Why do we need it?
Verifies pip packages being installed with hashes.

What testing is done?
Tested installing the affected packages via the modified script and able to successfully use them.
Successfully ran make verify, make test. make test-integration not available.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: echyam / name: Elizabeth Yam (1a0d49c)

[k8s-ci-robot]

Welcome @echyam!

It looks like this is your first PR to kubernetes-sigs/aws-ebs-csi-driver 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/aws-ebs-csi-driver has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @echyam. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[AndrewSirenko]

@echyam thank you for your PR, but I believe you need to sign the CLA

See this comment: #2012 (comment)

[ConnorJC3]

/ok-to-test

Thanks for signing the CLA, will try to get this reviewed next week

[github-actions]

Code Coverage Diff

File	Old Coverage	New Coverage	Delta
github.com/kubernetes-sigs/aws-ebs-csi-driver/pkg/cloud/cloud.go	84.1%	85.4%	1.3
github.com/kubernetes-sigs/aws-ebs-csi-driver/pkg/metrics/metrics.go	66.7%	72.0%	5.3

[echyam]

@ConnorJC3 any chance of update this week?

[ConnorJC3]

Sorry, got busy last week

/lgtm

[AndrewSirenko]

Thanks for this best-practice.

[ConnorJC3]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ConnorJC3

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:

• OWNERS [ConnorJC3]

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