Build status in build page shows wrong conclusion

[premun]

Example: https://maestro.dot.net/channel/8297/github:dotnet:aspnetcore/build/297377
This is a failing build and there are newer successful builds but the message says:

This is the most recent successful build, more recent builds are failing

It is not successful and there are more recent successful builds

[adamzip]

The logic for this definitely has some mistakes like the one quoted in the issue description, that can be easily fixed.
But more than that, the logic is mixing the specific build's success with the state of the most recent builds into some amalgamated status in a bit of a strange way.

It seems like #5848 (comment) might already include some good info about recent build statuses, so maybe we can get rid of it in this specific barviz component, and simply display green for successful build and red for failing one.

[adamzip]

After offline discussion, we agreed to think about this issue after designing #5848.
If the features added in #5848 add sufficient info about a subscription's (or repo's) recent build health, we can change the status on the build info page to simply show green / red depending on build success.

The status in this task has 3 states (green, blue, orange), but it seems unclear what we should show in certain situations.
Eg: the build succeeded, so you want to show green, but the most recent build failed, so you want to show that there's a problem (so should it be blue? orange? it's a bit confusing)

I think if we add some barviz features that show the "build health" or "codeflow health" of subscriptions, then we can separate the status for the build itself, and the status for the subscription in general.
and then we can have unambiguous green / red status for builds, and more complex statuses for subscriptions