Test Result Analyzer fails if no stack trace is available

[FreundDK]

❔What, Why & How

Fixes #2256

TestResultAnalyzer uses "#Text", which might be null instead of InnerText
This code shows what is wrong with that:

# Demonstrates the bug fixed by this PR:
# ."#text" returns $null on empty XML elements, causing .Trim() to throw.
# .InnerText returns "" instead, handling empty nodes safely.

[xml]$xml = @"
<nodes>
  <node message="1">Content</node>
  <node message="2"></node>
</nodes>
"@

Write-Host -ForegroundColor Yellow "FAILING:"
try {
    foreach ($node in $xml.nodes.node) {
        Write-Host "$($node.message)"
        Write-Host "Content: '$($node."#text".Trim())'"
    }
}
catch {
    Write-Host -ForegroundColor Red "ERROR"
}
Write-Host
Write-Host -ForegroundColor Yellow "WORKING:"
foreach ($node in $xml.nodes.node) {
    Write-Host "$($node.message)"
    Write-Host "Content: '$($node.InnerText.Trim())'"
}

[Copilot]

Pull request overview

Fixes a crash in the AnalyzeTests action when a <failure> XML element has no stack trace content by switching from the XML "#text" accessor (which can be $null) to InnerText (empty string for empty nodes).

Changes:

• Replace $failure."#text" with $failure.InnerText when rendering and storing stack traces in GetTestResultSummaryMD.

[aholstrup1]

LGTM. Missing a releasenote though