Increasing scan resiliency by gracefully handling errors during scans

[lior-orca]

Generally, and lately, there are cases of scan failures (e.g. panic errors) due to invalid IaC files or missing files.
Examples of related issues/PRs
#6519
#6510
#6511
#6381

What we can do to mitigate the problem, is to have a generic code to skip such cases, instead of failing the whole scan (when thinking of it thoroughly, such files are already 'broken' so finding issues in them is less important)

2 main options to address such logic -

1. Always skip while adding warning log
2. Add a "strict mode" (or "soft mode") CLI flag. This will give the user the ability to control it.
   e.g. if using --strict it will result in scan failures, due to such an unknown issue, while the regular mode will pass

[lior-orca]

Related PR - #6527