feat(reachability): skip uploading invalid files

[paulrosca-snyk]

Pull Request Submission Checklist

• Follows CONTRIBUTING guidelines
• Commit messages
  are release-note ready, emphasizing
  what was changed, not how.
• 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: ___)
• Includes product update to be announced in the next stable release notes

What does this PR do?

Changes the behaviour of snyk test --reachability and snyk sbom test --reachability so that the commands no longer fail when uploading the source code if there are invalid files inside the directory.

Where should the reviewer start?

How should this be manually tested?

Running snyk test --reachability/snyk sbom test --reachability inside a directory with invalid files (e.g broken symlinks) should result in a test running and results being displayed.

What's the product update that needs to be communicated to CLI users?

snyk test --reachability/snyk sbom test --reachability will no longer fail when uploading the source code if there are invalid files inside the directory, instead the invalid files will be skipped and debug logs will indicate the reason (if -d is provided).

Risk assessment (Low | Medium | High)?

Low - this only affects customers which have access to --reachability and the files which we skipped uploading will now show in debug logs.