Show more comprehensive background processing progress notifications

[peppy]

Addresses the visibility part of #25824. Will attempt to reduce the side-effects at song select separately.

CleanShot.2023-12-18.at.09.43.29.mp4

[bdach]

this is a bit of a crime but i'm not gonna split hairs for now as none of this is correctly localisable anyways (no pluralisation support)

[peppy]

split hairs 😎

yeah i dunno, it's isolated and can be refactored if/when we manage to localise this.

[bdach]

The above is a nit, but the bigger problem here is the tests. They are presumably failing because these notifications will now show up on a blank install.

In fact, this is what shows up on a completely clean lazer environment (after rm -rfing the data directory):

This is because the processing is running on the fake "triangles" beatmap.

We probably don't want that. One thing that could be done is this:

diff --git a/osu.Game/BackgroundDataStoreProcessor.cs b/osu.Game/BackgroundDataStoreProcessor.cs
index 55be7f2c9e..9d2a719957 100644
--- a/osu.Game/BackgroundDataStoreProcessor.cs
+++ b/osu.Game/BackgroundDataStoreProcessor.cs
@@ -135,12 +135,12 @@ private void processBeatmapSetsWithMissingMetrics()
                 // of other possible ways), but for now avoid queueing if the user isn't logged in at startup.
                 if (api.IsLoggedIn)
                 {
-                    foreach (var b in r.All<BeatmapInfo>().Where(b => (b.StarRating < 0 || (b.OnlineID > 0 && b.LastOnlineUpdate == null)) && b.BeatmapSet != null))
+                    foreach (var b in r.All<BeatmapInfo>().Where(b => (b.StarRating < 0 || (b.OnlineID > 0 && b.LastOnlineUpdate == null)) && b.BeatmapSet != null && !b.BeatmapSet.Protected))
                         beatmapSetIds.Add(b.BeatmapSet!.ID);
                 }
                 else
                 {
-                    foreach (var b in r.All<BeatmapInfo>().Where(b => b.StarRating < 0 && b.BeatmapSet != null))
+                    foreach (var b in r.All<BeatmapInfo>().Where(b => b.StarRating < 0 && b.BeatmapSet != null && !b.BeatmapSet.Protected))
                         beatmapSetIds.Add(b.BeatmapSet!.ID);
                 }
             });
@@ -196,7 +196,7 @@ private void processBeatmapsWithMissingObjectCounts()
 
             realmAccess.Run(r =>
             {
-                foreach (var b in r.All<BeatmapInfo>().Where(b => b.TotalObjectCount == 0))
+                foreach (var b in r.All<BeatmapInfo>().Where(b => b.TotalObjectCount == 0 && b.BeatmapSet != null && !b.BeatmapSet.Protected))
                     beatmapIds.Add(b.ID);
             });
 

but I don't know...

[peppy]

I've applied the proposal in a bit of a more central way, good catch.

[peppy]

Turns out that solution plays pretty bad because IQueryable doesn't work well on children objects. So I've taken the alternative approach of only showing notifications when there's enough items for it to matter.