Fix angle brackets not shown correctly in Git blame tooltip

[camc314]

This originally broke in f633b12, this commit simply replaced < and > characters with their HTML encoded equivalents. While this worked, it was not correct for the case where < or > exist inside code blocks.

This also felt confusing that this was not happening where the markdown was being parsed, but rather where where the blame message was retrieved from git.

This commit fixes #22044, and should not cause a regression in #16220, by pushing any InlineHtml to the resulting string after parsing the markdown.

Closes #22044

Release Notes:

• Fixed an issue where angle brackes would not be rendered correctly if nested inside a codeblock in git blame

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[cole-miller]

Thanks for the PR! +1 to removing the special-case escaping of angle brackets. But we need a different approach for this inside the markdown parser, since emails in <> show up as Tag::Link not Event::Html, e.g. for this commit message

test

Line 1
Line 2

Signed-off-by: somebody <[email protected]>

we get

Start(Paragraph)
Text(Borrowed("test"))
End(Paragraph)
Start(Paragraph)
Text(Borrowed("Line 1"))
SoftBreak
Text(Borrowed("Line 2"))
End(Paragraph)
Start(Paragraph)
Text(Borrowed("Signed-off-by: somebody "))
Start(Link { link_type: Email, dest_url: Borrowed("[email protected]"), title: Borrowed(""), id: Borrowed("") })
Text(Borrowed("[email protected]"))
End(Link)
End(Paragraph)

So we just need to tweak the handling of Tag::Link when the LinkType is Email. Would you be up for revising this to use that approach?