Initiate error upon partial missing components when constructing Yarn V1 dep tree

[eranturgeman]

• The pull request is targeting the dev branch.
• The code has been validated to compile successfully by running go vet ./....
• The code has been formatted properly using go fmt ./....
• All static analysis checks passed.
• All tests have passed. If this feature is not already covered by the tests, new tests have been added.
• Updated the Contributing page / ReadMe page / CI Workflow files if needed.
• All changes are detailed at the description. if not already covered at JFrog Documentation, new documentation have been added.

---

depends on: jfrog/build-info-go#285

[attiasas]

LGTM, you can add a test that generate an error for coverage

[github-actions]

---

🐸 JFrog Frogbot

[github-actions]

Merging this branch will not change overall coverage

Impacted Packages	Coverage Δ	🤖
github.com/jfrog/jfrog-cli-security/commands/audit/sca/yarn	0.00% (ø)

---

Coverage by file

Changed files (no unit tests)

Changed File	Coverage Δ	Total	Covered	Missed	🤖
github.com/jfrog/jfrog-cli-security/commands/audit/sca/yarn/yarn.go	0.00% (ø)	0	0	0

Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code.

Changed unit test files

• github.com/jfrog/jfrog-cli-security/commands/audit/sca/yarn/yarn_test.go