Support multiple tracking issues linked to a single github issue

[dibarbet]

There are cases where we find a new, slightly different failure that is not part of the query for an existing tracking issue, but it is the same cause. Currently linking two tracking issues to the same github issue will cause the new one to overwrite all the failed build information with the newly linked tracking issue builds.

Example:
dotnet/roslyn#52658 - I had to manually get back the failures from TupleWithElementNamedWithDefaultName when I associated it with IndexOfUnderlyingFieldsInTuple9.

Alternatively, allowing editing (#146) plus allowing multiple queries (or allow queries to search multiple tests like TupleWithElementNamedWithDefaultName OR IndexOfUnderlyingFieldsInTuple9) would also resolve this issue