Command Summary - New record functionality

[EyalDelarea]

• All tests passed. If this feature is not already covered by the tests, I added new tests.
• All static analysis checks passed.
• This pull request is on the dev branch.
• I used gofmt for formatting the code before submitting the pull request.

---

In addition to the existing simple data recording function, we now have the capability to record data with a predefined 'index'. This allows us to categorize and store specific information that can be easily accessed by other components within the summary report.

The main example of this usage is storing indexed scan results, which can later be attached to specific files in the summary.

Here’s an example of how to use the new function:

err = buildInfoSummary.RecordWithIndex("myBuildScanData", BuildScan, BuildName,BuildNumber)

Will resolve to a file system like this:

The supported indexes so far are:

1. Build Scan
2. Binaries Scan
3. Docker Scan
4. Sarif Report

Note

This change also requires that the generation of markdown will happen via a CLI command, rather than automatically. The PR in the CLI will introduce a new command called "create-summary-markdown".

[eyalbe4]

The entire commandssummaries package is located directory under the artifactory/commands package. This is wriwrongng, because commandssummaries isn't a command.
I therefore suggest moving the entire commandssummaries directory to be under artifactory/utils.

[github-actions]

---

🐸 JFrog Frogbot