Simplify getResultScanStatus

[eranturgeman]

• All tests passed. If this feature is not already covered by the tests, I added new tests.
• This pull request is on the dev branch.
• I used gofmt for formatting the code before submitting the pull request.
• Update documentation about new features / new supported technologies

---

This PR simplify the getResultsScanStatus by stop considering several SecurityCommandResults.
Since we Deprecated the Projects and WorkingDirs concepts, it seems like we cannot get several scan results from a single run, therefore we take the scans statuses from the single scan we have.

[github-actions]

---

🐸 JFrog Frogbot

[eyalk007]

only thing to check is to validate if working dir isnt coming back as a concept next q

if it does maybe the simplification isnt worth it
@eranturgeman @orto17

[eranturgeman]

only thing to check is to validate if working dir isnt coming back as a concept next q

if it does maybe the simplification isnt worth it @eranturgeman @orto17

This question if in place but if it does come back soon - we need to think if having separate working dirs means separate scans. if not - we still only have one set of results. if we do perform separate scans (I think we should in order to enable defining different settings to different parts of the repo, the cc "modules") so Eyal is correct and this change is not valid
@orto17

[eyalk007]

lets discuss with or about the nil check