Bug: Successful check hides failed check of same name

Expected Behavior

If a PR has 2 check runs with the same name, and one fails and one succeeds, after they both finish

• "#check-failure=1" should be true
• "#check-success=1" should be true

Actual Behavior

Tested with the Mergify config editor against a more complex PR that has been closed and merged, effectively the results are

• "#check-failure=1" is false
• "#check-failure=0" is true
• "#check-success=1" is true

Steps to Reproduce the Problem

1. Create two workflows (different files) with the same job name. One workflow always succeeds, one workflow always fails.
2. Use a Mergify configuration with condition checking for zero pending, 1 failure, 1 success.
3. See that the condition is never satisfied, because at the end of the runs, "#check-failure=1" is false.

Specifications

More details in this discussion

Start with the linked discussion and reproduce the issue using two workflows with the same job name, one succeeding and one failing. Trace how the Mergify configuration evaluates #check-failure and #check-success for those GitHub check runs; done means both conditions report a count of one.