Tests which have been re-ran to update results to avoid conflicts between testers still incorrectly display conflicting results

[Paul-Clue]

On the Test Queue page (/test-queue), there are test plans showing conflicts even though multiple testers have the same test results. The problem is that, somehow, some tests that end up with an unexpected behavior ID of "EXCESSIVELY VERBOSE" end up with otherUnexpectedBehaviorText in unexpectedBehavior array. The otherUnexpectedBehaviorText should not be there.

This PR removes the otherUnexpectedBehaviorText from unexpectedBehavior arrays that are already in the database and it prevents the problem from occurring in future test plans.

[howard-e]

Thanks @Paul-Clue, it looks good!

I've only left a comment about the info being logged.

[howard-e]

Just a thought, and not suggesting as something to act on as it's outside the scope of this PR.

Right now, the GQL context could be { user, atLoader, browserLoader } with the change in #623. Now that I've seen its usage a bit more, it seems atLoader and browserLoader being present is a must in most queries.

So I'd think that when context is null in the resolvers it's called, it may be preferred if it simply defaults to { atLoader, browserLoader }. I'm unsure if sure if there's any implications to that though, and also acknowledge that it would a considerable effort in determining that. But creating the objects here to solely retrieve the conflict results here felt out of place.