Fixes Event Log Message Format on Unmanaged FailFast

[Silvenga]

We observed the following event log messages:

CoreCLR Version: 6.0.21.52210
.NET Version: 6.0.0
Description: The process was terminated due to an internal error in the .NET Runtime.at IP 01090791 (00F40000) with exit code 80131506.

We are still investigating the crashes, but in the meantime we noticed the message was a little off, this PR just fixes the fallback messages to match the newer versions in resources (assumed) to make the message read a bit nicer. 😸

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[danmoseley]

Being picky, it seems to me that IP 01090791 (00F40000) with exit code 80131506. ought to be IP 0x01090791 (0x00F40000) with exit code 0x80131506. so it's clear they're all hex.

This formats with %p, %p and %x respectively. A gotcha is %p prefixes 0x when I try with clang, and not when I try with cl. %x is never prefixed.

[danmoseley]

Test failure fix is in #63529

[Silvenga]

@danmoseley - I updated the formats with 0x%x to match other places that hex is being formatted, that seems to be the most portable approach.

[jkotas]

Thank you!

[Silvenga]

Unrelated, the crashes were caused by us 😭 - slight incompatibility with changes in the span implementation in .NET 6 😆.