OLS-1384: Update requirements.txt

[onmete]

Description

Update requirements.txt from the current lib set.
Fix the version too.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign joshuawilson for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[tisnik]

should be it part of #2154 ?

[onmete]

Nope, that one is too hard to make happen.

[xrajesh]

Looks good - but I am missing the to understand , what is driving this change - could you please post what is driving this change ? Thank you @onmete

[openshift-ci-robot]

@onmete: This pull request references OLS-1384 which is a valid jira issue.

In response to this:

Description

Update requirements.txt from the current lib set.
Fix the version too.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@onmete: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/4.17-images	24fffd3	link	true	/test 4.17-images
ci/prow/fips-image-scan-service	24fffd3	link	true	/test fips-image-scan-service
ci/prow/4.15-images	24fffd3	link	true	/test 4.15-images
ci/prow/4.17-e2e-ols-cluster	24fffd3	link	true	/test 4.17-e2e-ols-cluster
ci/prow/images	24fffd3	link	true	/test images
ci/prow/4.16-images	24fffd3	link	true	/test 4.16-images

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.