Associating failures with runfo issues is unreliable

[sbomer]

Forgive me if this is a user error - I am still new to runfo. I noticed two problems:

1. Runfo did not populate the list of failures in an associated github issue.
2. Runfo removed failures from a github issue after I manually associated builds with issues in runfo.

Here's what I did:

• This build failed with a known issue: https://runfo.azurewebsites.net/view/build/?number=1581468
• Clicking on the failing testcase shows a history of failures: DebuggerTests.AssignmentTests.DebuggerTests.AssignmentTests.InspectVariableBeforeAndAfterAssignment
• At the bottom of the list, "Create Issue" creates a runfo issue – I associated it with the github issue [wasm][debugger] DebuggerTests.AssignmentTests.InspectVariableBeforeAndAfterAssignment failing dotnet/runtime#64188, but it did not populate the list of failures in the github issue.
• I manually went through builds and associated each one that had the same failure to the github issue in runfo. This caused the github issue to be updated with the associated failing builds.
• ...but an hour later I checked and the table of associated builds had been cleared in the github issue.