feat(test, monitor): python pip support for local wheel files specifiers

[gemaxim]

Pull Request Submission Checklist

• Follows CONTRIBUTING guidelines
• Includes detailed description of changes
• Contains risk assessment (Low | Medium | High)
• Highlights breaking API changes (if applicable)
• Links to automated tests covering new functionality
• Includes manual testing instructions (if necessary)
• Updates relevant GitBook documentation (PR link: ___)

What does this PR do?

It bumps the snyk-python-plugin package, introducing the following:

• Adds support for local wheel files specifiers in requirements.txt files. These scenarios were previously failing. - feat: [OSM-2206] support for local whl files req specifier snyk-python-plugin#254
• A minor fix to skip unparsable/failing lines in requirements.txt when testing using --skip-unresolved flag. Example: when the client specifies a path that doesn't exist. - fix: [OSM-2206] skip unresolved local packages snyk-python-plugin#255

Where should the reviewer start?

The linked PRs mentioned above. The existing acceptance tests for python projects in the cli, as well as the tests added in the plugin cover these changes.

The changed acceptance tests for newly supported local whl files.

The automated tests for the plugin support for whl files:

• snyk/snyk-python-plugin@e8b6e84#diff-b6529c5b65bc9058b646385cc48c291f4760c7182462076d69bbc7d3ffd39421
• https://github.com/snyk/snyk-python-plugin/pull/254/files#diff-b6529c5b65bc9058b646385cc48c291f4760c7182462076d69bbc7d3ffd39421R133

How should this be manually tested?

Create a python project similar to the test fixture added in the PR - snyk/snyk-python-plugin@b42e5fc#diff-2944fcfe76ba8f2b7aa23aac36d2636586d68247619b29a259533d36255cfd27.
Run pip install -r requirements.txt.
Run snyk test --comand=python3 and receive a successful response.

What are the relevant tickets?

https://snyksec.atlassian.net/browse/OSM-2206

[thisislawatts]

I am curious about this statement;
and the existing acceptance tests for python projects in the cli, as well as the tests added in the plugin cover these changes.
If there are tests in the CLI repo which test this behaviour why have there been no changes, or additions, to the tests to capture the new functionality?

[gemaxim]

I am curious about this statement; and the existing acceptance tests for python projects in the cli, as well as the tests added in the plugin cover these changes. If there are tests in the CLI repo which test this behaviour why have there been no changes, or additions, to the tests to capture the new functionality?

@thisislawatts I think the interaction between cli and the plugin is the same. I might have used functionality wrong, as these are changes for supporting a very specific type of dependencies accepted by pip. If we add acceptance tests for all these cases, we would have duplicated the tests in the plugin. The basic functionality of the plugin is the same: returning dep graphs for requirements.txt input files.

[gemaxim]

@thisislawatts I updated the tests here after I merged this PR