keep original file order

[barv-jfrog]

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

---

[hadarshjfrog]

can you use github.com/virtuald/go-ordered-json instead? want to keep same git sources when we can

also - please keep the breaklines in the GO - so all of the jfrog ones will be together, all the github ones if possible (I see "github.com/jfrog/jfrog-cli-security/utils/results/output" was moved unnecessarily

[barv-jfrog]

changed package but order is predetermined

[github-actions]

Merging this branch will not change overall coverage

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

---

Coverage by file

Changed files (no unit tests)

Changed File	Coverage Δ	Total	Covered	Missed	🤖
github.com/jfrog/jfrog-cli-security/commands/enrich/enrich.go	0.00% (ø)	0	0	0
github.com/jfrog/jfrog-cli-security/utils/utils.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.