fix: Skip specific errors when parsing yaml IaC files

[ipapast]

• Follows CONTRIBUTING rules

What does this PR do?

We identified a few cases that our services parse the yaml files in a different way. The node 'yaml' library is too 'strict', returning errors for validation of the YAML as well.

In this PR we focus on two specific errors: bad indentation and duplicate keys.
These two examples are not consistent with what Policy Engine returns so in this commit we intentionally skip errors for these cases, and return the parsed YAML document instead.

This will improve the consistency between the two parsers.

Where should the reviewer start?

The changes are in file-parser.ts and iac-parser.ts where we check if the error is one of the two error strings.

How should this be manually tested?

• Create a file with a SemanticError, e.g. duplicate keys:

apiVersion: v1
kind: Pod
metadata:
  name: myapp-pod
spec:
  containers:
  something: here
metadata:
  another: thing

Run snyk-dev iac test duplicate_keys.yaml
See that it is no longer failing but showing results (if any).

What are the relevant tickets?

CC-927

Screenshots

Before:

After:

Additional questions

[ipapast]

@almog27 @teodora-sandu I extracted the check as a function and gave it a descriptive name, also added an extra test. If you could have a look again 🙇

[github-actions]

Expected release notes (by @ipapast)

fixes:
Skip specific errors when parsing yaml IaC files (49c184d)

others (will not be included in Semantic-Release notes):
get rid of changes from #1974 to fix broken test (217d1fa)
get npm to grab token directly from env (dcac487)
enforce prettier across entire project (6cb8953)
enforce eslint across entire project (d2aa5f5)
migrate to tempfile to tempy (5af6fdb)
upgrade to uuid@8 (1c65dd9)
let npm fetch the npm_token for us (12052e8)

• I hereby acknowledge these release notes are 🥙 AWESOME 🥙