Fix build scan command table printing with --vuln=true

[dortam888]

• 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.
• All changes are detailed at the description. if not already covered at JFrog Documentation, new documentation have been added.

---

Fixing issues when using --vuln=true flag and --format=table (default) in build scan.
Issue 1: build scan printed vulnerability table twice instead of printing the violation table and the vulnerabilities table.
Issue 2: The vulnerability table is messed up, not sorted, and shows the same vulnerability multiple times.

[hadarshjfrog]

after removing this line - did you test the CLI behaviour with and without watches?

[dortam888]

@hadarshjfrog I did the regular tests there is no watch test in jf build-scan (must have a watch with fail build policy).
This line doesn't affect watches as it relates to vulnerabilities. (and watches are affecting violations).
We call SetIncludeVulnerabilities in line 179 if vulnerabilities should be added.
https://github.com/jfrog/jfrog-cli-security/blob/main/commands/scan/buildscan.go#L180

[github-actions]

---

🐸 JFrog Frogbot

[attiasas]

This change is not how to fix the issue.
There are 2 issues here:

1. we can see that in the parsing of the flags, we don't take into account the project flag only in build-scan. the fix should add it, instead of removing and always printing violations...
   
   

2. In the table printing code, we do not expect to print both violations and vulnerabilities tables so we need to choose one (preferable vuln if requested)
   

[dortam888]

@attiasas @hadarshjfrog We have a couple of issues with jf bs.
Some parameters are missing, like projects and JAS enablement so we don't get results for builds from projects and we don't get JAS results at all (we don't have secrets but we can have CA).
Regarding this fix, See the comment in the code:
https://github.com/jfrog/jfrog-cli-security/blob/main/commands/scan/buildscan.go#L171
The behavior when the format is json for example is appending vulnerabilities to violations and that is what the code meant to do for tables as well based on the comment.
Jira is about having violations and no vulnerabilities try to get vulnerabilites.
The build is failing because we have violations but we're not showing it in tables printing.

[attiasas]

fixed in:

• Print both vulnerabilities and violations tables if needed #163
• Fix sorting table results when no JAS scan #164