fix flaky test results in TestOperationalRiskSimplifiedViolation test…

[dortam888]

… by soting the violations resulting from simplifyViolations function

• 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.

---

Fix Flaky behavior in the TestOperationalRiskSimplifiedViolation test that makes the test sometimes fail due to stability in the array when using the simplifyViolations function. If I have violations {violation1, violation2} after calling simplifyViolations(violations, true/false) the return value would be either {violation1, violation2} or {violation2, violation1}.
Sorting the array in order of the component key makes the result stable.

[github-actions]

---

🐸 JFrog Frogbot