fix: [CLI-942] Bumping snyk-docker-plugin

[dotkas]

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 bumps snyk-docker-plugin to it's newest version, following a somewhat turbulent attempt at doing this earlier last month. The snyk-docker-plugin contained some flawed logic when spawning subprocesses, and this new attempt does it following the NodeJS best practices. Namely, to not spawn subprocesses in a shell where avoidable.

Where should the reviewer start?

See this PR for the details: snyk/snyk-docker-plugin#686

How should this be manually tested?

Build the CLI locally using make build and try to do a snyk container test node:latest and check it succeeds correctly.

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

N/A, implementation optimization.

Risk assessment (Low | Medium | High)?

Medium: Our acceptance tests caught the issue last time, and I believe they are fairly covering. However, there is a risk that a logical path is not covered in the acceptance tests which could trigger an issue. But in general, I believe that if docker is able to be run and queried on all operating systems, through this plugin, it should work as expected.

[snyk-io]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

✅ code/snyk check is complete. No issues have been found. (View Details)