Don't compare `ArtifactLocation.Index` inside `MatchedResult` about sarif-sdk

[michaelcfanning]

Yes, this is clearly not correct. It raises the question as well, is the matcher properly dereferencing the artifact itself to determine whether there's been a change there that would warrant an 'updated' result (for example, if the artifact hash itself has changed). Complicated.

How much is this blocking you? I assume at this point you may have a workaround in the sense that you can simply treat updated as unchanged. Or are you building specific functionality around the updated state?

[dmitrykobets-msft]

currently this is not blocking me since my workaround involves merging together the artifact lists from both baseline and candidate using a hand-written less strict ArtifactEqualityComparer. I update the ArtifactLocation indices inside the baseline and candidate results accordingly. That way both candidate and baseline will share the same artifact lists and indices so the baselineState won't be incorrectly set to updated.