Add commit staleness to maestro++ UI

[davidfowl]

Today we can see the build staleness but it would also be good to look at commit staleness. It would give you a nice way to see at glance how far behind a particular dependency is in terms of commits (especially if builds are failing);

cc @mmitche

[mmitche]

@Pilchie pointed us at this code which uses the GitHub API to compute the commit distance (without the repo) https://github.com/Pilchie/DependencyFlow/blob/master/Pages/Incoming.cshtml.cs#L186-L229

I believe that AzDO has similar fields in its comparison APIs

[MattGal]

[Triage] : looks reasonably straightforward to add as data we track, but not sure what epic it'd go in nor if it's worth the effort as build number / staleness is at likely to be strongly correlated. Definitely not an FR issue.

[davidfowl]

Except its not. When there are failing builds this shows nothing that indicates how long builds have been failing

[riarenas]

Looks like a reasonable ask. Since we don't have a workstream for for dependency flow features right now, I think we should assign it to https://github.com/dotnet/arcade-services/issues/2570 when it's funded.

[ChadNedzlek]

I'm worried that epic is becoming a sort of... hodge podge of stuff that's going to make it difficult to fund/execute. :-(

[ChadNedzlek]

Fixed title/description, since I'm pretty sure it's talking about "staleness", not "stateless"

[davidfowl]

I was getting excited because I thought we did the feature 😄

[markwilkie]

Moving to dotnet/arcade-services#2570 - and sorry @davidfowl, it's not funded yet.....