Fix results screen fetching scores twice when scrolled to edge

[frenzibyte]

• Depends on Fix daily challenge abruptly discarding score selection when opening results screen #29058 to be able to test this in game

This one is not necessarily tied to daily challenge but it's something I noticed and it didn't feel well.

The fix here is, well, a schedule... Here's the order of how things happen:

1. ResultsScreen.Update notices user is scrolled to beginning/end and fetches scores, blocking further fetches with lastFetchCompleted
2. The scheduled logic in fetchScoresCallback is invoked, resetting lastFetchCompleted
3. ResultsScreen.Update is called with lastFetchCompleted state reset, therefore incorrectly fetching more scores.

The fix is to schedule resetting lastFetchCompleted just one frame after adding the scores, so that the scroll container's state is updated before checking whether it's scrolled to beginning/end.

Before:

CleanShot.2024-07-25.at.09.16.46.mp4

After:

CleanShot.2024-07-25.at.09.17.48.mp4

[bdach]

You know what I think of fixing things via schedules...

Is using UpdateAfterChildren() or something not an option here?

[smoogipoo]

Let's go with this for now. I don't like using schedule to fix stuff like this either, but I think using UpdateAfterChildren() is going to be even more complex/uglier/error-prone.

At the end of the day, this is an o!f layout issue and not an easy one to solve at that.