Fix bugs when converting results to SARIF

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

---

Fixing the following bugs when parsing the results to SARIF format

Duplicate [Secret in Binary found]

• Some attributes were not copied when parsing to format, when parsing for the second time it already was "padded" with the prefix which resulted in duplicate "padding"

Uri attribute is empty on binary scan

  "locations": [
           {
             "physicalLocation": {
               "artifactLocation": {
                 "uri": ""
               }
             },
             "logicalLocations": [
               {
                 "name": "38610c0cfc18becc30c87e0af68f1c43c5cdc0ef10d920dde284df0d58fb00e1",
                 "kind": "layer",
                 "properties": {
                   "algorithm": "sha256"
                 }
               }
             ]
           }
         ],

• For Docker targets (and some binaries), the target.Target is a file and not a directory and we set it as the wd of the SCA Sarig run, when we are translating the results location to relative paths it had uri=wd which resulted in leaving empty value

[github-actions]

---

🐸 JFrog Frogbot

[hadarshjfrog]

Just my take - not crucial - but I'd keep the name close to target (t, actualTarget, etc)

[hadarshjfrog]

Code is fine - please add an explanation to the PR desc to explain the change in the satif copy mechanism