Extract code snippet into stand alone component

[charisk]

Extracts components and logic that help us render code snippets out of AnalysisAlertResult and into a new stand-alone component so that it can be re-used when showing code paths for problem path queries.

The code is mostly a copy of what has been checked in but with a few adjustments:

• Improved styling
• Improved highlighting for multi-line highlights
• It no longer receives an alert model
• The "message" part is been made optional, with the ability to receive more children (this is where we'll plug in the code paths link for problem path queries).

Note that AnalysisAlertResult is really quite thin now and could be incorporated back into RemoteQueries.tsx but I think it'll get a bit more meat to it once we do code paths.

Checklist

N/A:

• CHANGELOG.md has been updated to incorporate all user visible changes made by this pull request.
• Issues have been created for any UI or other user-facing changes made by this pull request.
• [Maintainers only] If this pull request makes user-facing changes that require documentation changes, open a corresponding docs pull request in the github/codeql repo and add the ready-for-doc-review label there.

[aeisenberg]

Approving, assuming you will fix the typo. :)

My comment about the correctness of the locations can be done in the future.

[aeisenberg]

Going back to our conversation on the previous PR about handling invalid source locs, there are a number of common errors that I think you can handle right here:

if (highlightStartColumn > highilightEndColumn) {
  ([highlightStartColumn, highilightEndColumn] = [highilightEndColumn, highlightStartColumn]);
}

highlightStartColumn = Math.max(highlightStartColumn, 0);
highilightEndColumn = Math.max(highlightStartColumn, highilightEndColumn);

Or some variant of this. It looks like this code won't cause an error if the locations are invalid, but they might cause missing highlights. Again, this is pretty rare, but it does happen.

[charisk]

Thanks for the example/code. Lets discuss validation next week!

[aeisenberg]

Typo: highilightEndColumn -> highlightEndColumn