Refactor commands output formats

[attiasas]

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

---

Move all Results and outputs to their inner package, organize currently available code and renames to fit better.

Before:

After:

Move detection out of SCA to run first thing in audit

• Allows to sync information from local jfrog-apps-config.
• Prepare to remove config detection to separate command.
• Prepare to remove dependency collection to separate command.

Change Results object to ScanCommandResults

• Prepare the infrastructure to separate different sca children-targets in a single scan target
  

Separate converting ScanCommandResults to different output formats and printing the output.

• output package - Write the results in a specific format as an output string.
• conversion package - Parse the ScanCommandResults object to convert it to different formats that we are supporting.

Make implementing a new output format (by introducing an interface) easier, and maintain the currently supported.

• Reduce code duplications
• Easy to see what we support
• Easy to implement new formats / integrate new scans and results
  

General validation improvments for results structs

• Easy to support and maintain
• Adds more tests
• Exact/Partial match options (for unit + integration tests)
• Easy to read what is tested
• Refactor validations to its own package