fix: apply ignores correctly for .snyk excludes

[j-luong]

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?

This PR fixes two issues related to .snyk ignores created via the snyk ignore command:

• ignores that included a reason and/or expiry are now being ignored as expected
• ignores that used an absolute path instead of a relative path are now being ignored as expected

Where should the reviewer start?

How should this be manually tested?

In a project with Snyk Code issues:

• Create ignore with a valid expiry
  • snyk ignore --expiry=3026-1-1 --reason="testing" --file-path=<absolute/path/to/file>
  • Run snyk code test
  • Validate ignored file is ignored
• Create an expired ignore
  • snyk ignore --expiry=1999-1-1 --reason="testing" --file-path=<absolute/path/to/file>
  • Run snyk code test
  • Validate ignored file is not ignored

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

Ignores created via the snyk ignore command are now correctly applied if an expiry is set or if using an absolute filepath

[github-actions]

	Warnings
⚠️	Since the CLI is unifying on a standard and improved tooling, we're starting to migrate old-style imports and exports to ES6 ones. A file you've modified is using either module.exports or require(). If you can, please update them to ES6 import syntax and export syntax. Files found: test/jest/acceptance/snyk-code/snyk-code-user-journey.spec.ts

Generated by 🚫 dangerJS against a61589c