fix: handle malformed URIs

[MonsieurCo]

Fixing issue of parsing error when encountering malformed URI
example
scanning and uploading to ssc this project with opengrep with a SARIF output
result in this error :

Exception: An unexpected error occurred during scan processing: com.fortify.manager.exception.FMScanParseException:
Parsing error while parsing scan vulnerabilities: Cannot deserialize value of type 'java.net.URI' from String "2_Server 
Streaming/client/client.js": not a valid textual representation, problem: Illegal character in path at index 8: 2_Server 
Streaming/client/client.js at [Source: (com.fortify.util.io.RegionInputStream); line: 1, column: 3213] (through reference 
chain: com.fortify.ssc.parser.sarif.domain.Result["locations"]->java.lang.Object[][0]-
>com.fortify.ssc.parser.sarif.domain.Location["physicalLocation"]-
>com.fortify.ssc.parser.sarif.domain.PhysicalLocation["artifactLocation"]-
>com.fortify.ssc.parser.sarif.domain.ArtifactLocation["uri"]); session b8mvd7v78ni6a

the SARIF output from opengrep is correct because parsed correctly by other parsers (eg: VScode SARIF viewer )

i have build the the fix and installed on my fortify version and the error is gone.

files causing issue present in this comment #37 (comment) if you want to reproduce.

Ps : i've fulfilled the form for contributing on this project in CONTRIBUTING.md

[Romain-Geissler-1A]

I don't know java at all, but isn't there already some builtin library utility to parse uri encoded data, rather than doing it manually ?

[MonsieurCo]

you have a good point on that,

i am not an experimented developer in java and at first I considered using URLEncoder but i am not sure if i would not introduce some sort of bugs since it's designed for form data it replaces spaces with + instead of %20 (where i learned that ) , which could break file paths or URIs.
since in SARIF follow the standard https://docs.oasis-open.org/sarif/sarif/v2.1.0/errata01/os/sarif-v2.1.0-errata01-os-complete.html#_Toc141790680 in the RFC3986 says that it should be encoded in percent

that's why i went in a naïve approach to be sure i would not rely on a unknown decision from a library that could not be compliant with the sarif format.

i can look for that library but it seems not in standalone
i found again on stackoverflow a post talking about the issue and someone is advising to use uriencode from springframework
and that might be too much to add no ?

[MonsieurCo]

Ps:
I made sure that the code is parsing correctly others non-alphanumeric characters without crashing.