fix: Only include CollectionJob metrics in Bot Status calculation on Test Queue page when tester.isBot is true

[howard-e]

This PR is to address the case in which a bot run is assigned to a manual user to be evaluated, and then a bot is assigned a run on the same report again. It would cause an aggregation of the assigned bot's and the previously assigned tester's results which would create confusing metrics in the Bot Status calculation, on the Test Queue page.

[jugglinmike]

Hey @howard-e, this looks good to me, and it works on my machine. I recognize that we're not convinced that this particular situation (a human user with a collectionJob attribute) ought to be allowed. I added a test anyway because it strengthens the evidence that your patch has the intended effect. Because that makes me the last one to touch this branch, though, I'm going to leave merging to you.

[howard-e]

I added a test anyway because it strengthens the evidence that your patch has the intended effect. Because that makes me the last one to touch this branch, though, I'm going to leave merging to you.

Good call! It definitely does. There was a missing collectionJob attribute error being thrown in the console with that added test. So it needed a small fix to include the human's status and testStatus attributes under collectionJob.

Will merge and deploy once the build is successful.

[jugglinmike]

Oh, nice, thanks!