fail build for violation context

[hadarshjfrog]

• 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.
• Updated the Contributing page / ReadMe page / CI Workflow files if needed.
• All changes are detailed at the description. if not already covered at JFrog Documentation, new documentation have been added.

---

This PR includes a bug fix for the following issue:
So far, when a user added --vuln flag we used to move to "vulnerabilities context", therefore ignoring fail build rules in discovered violations.
According to the documentation this flag means: "Set to true if you'd like to receive all vulnerabilities, regardless of the policy configured in Xray."
Therefore, this flag is expected to affect display ONLY and present vulnerabilities along with the violations when the flag is provided, but should not change any existing violations logic, meaning - if we have a FailBuild rule it should be applied even when the flag is provided with 'true' value

Known failing tests:

[github-actions]

---

🐸 JFrog Frogbot

[github-actions]

Merging this branch will not change overall coverage

Impacted Packages	Coverage Δ	🤖
github.com/jfrog/jfrog-cli-security	0.00% (ø)
github.com/jfrog/jfrog-cli-security/commands/audit	0.00% (ø)
github.com/jfrog/jfrog-cli-security/commands/scan	0.00% (ø)

---

Coverage by file

Changed files (no unit tests)

Changed File	Coverage Δ	Total	Covered	Missed	🤖
github.com/jfrog/jfrog-cli-security/commands/audit/audit.go	0.00% (ø)	0	0	0
github.com/jfrog/jfrog-cli-security/commands/scan/scan.go	0.00% (ø)	0	0	0

Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code.

Changed unit test files

• github.com/jfrog/jfrog-cli-security/git_test.go
• github.com/jfrog/jfrog-cli-security/scans_test.go