Fix CLI Execution from processing results twice

[kmcdon83]

… for both/all scanners will need future consideration

By submitting a PR to this repository, you agree to the terms within the Checkmarx Code of Conduct. Please see the contributing guidelines for how to create and submit a high-quality PR for this repo.

Description

CLI Execution was processing results twice. This change will resolve this.

Logic was removed related to Future processing as the scans were not properly Async compatible. This should be handle in the future.

Testing

Manual testing against GitLab and GitHub were conducted to validate the fix.

Checklist

• I have added documentation for new/changed functionality in this PR (if applicable). If documentaiton is a Wiki Update, please indicate desired changes within PR MD Comment
• All active GitHub checks for tests, formatting, and security are passing
• The correct base branch is being used

[cxflowtestuser]

Scan submitted to Checkmarx

[ofersk]

I will update my branch with the changes done in this commit.
@kmcdon83 we need to show you the change I'm implementing (basically, moving the logic in this commit to the vulnerabilityScanner)

[ofersk]

FYI, @AvivCx and @kmcdon83 there is a potential null pointer in the code (in all new functions, fixed on my branch).
if(flowProperties.getEnabledVulnerabilityScanners() == null || ... // <-- implies nullable
if(flowProperties.getEnabledVulnerabilityScanners().contains(SCA_SCANNER)) // <-- null pointer here