Ensure scores are re-fetched with correct criteria on re-entering song select

[bdach]

Closes #34445.

The primary issue is that song select is the only one that supports non-score sort mode, and therefore if any other component changes the sort mode in a way opaque to song select to score, then song select will lose the sort mode because it's using the global leaderboard manager's state which will contain scores sorted by total.

Notably, the bug this is fixing requires specific circumstances. For instance, getting the bug to present requires going through the results screen; it is not enough to just start gameplay for the bug to manifest, because starting gameplay causes a working beatmap refetch:

osu/osu.Game/Screens/SelectV2/SongSelect.cs

Lines 456 to 457 in 4b73afd

	// Forced refetch is important here to guarantee correct invalidation across all difficulties (editor specific).
	Beatmap.Value = beatmaps.GetWorkingBeatmap(beatmap, true);

which will trigger a delayed schedule refetch of the scores:

osu/osu.Game/Screens/SelectV2/BeatmapLeaderboardWedge.cs

Lines 235 to 253 in d2d3d14

	refetchOperation = Scheduler.AddDelayed(() =>
	{
	var fetchBeatmapInfo = beatmap.Value.BeatmapInfo;
	var fetchRuleset = ruleset.Value ?? fetchBeatmapInfo.Ruleset;
	var fetchSorting = Scope.Value == BeatmapLeaderboardScope.Local ? Sorting.Value : LeaderboardSortMode.Score;
	// For now, we forcefully refresh to keep things simple.
	// In the future, removing this requirement may be deemed useful, but will need ample testing of edge case scenarios
	// (like returning from gameplay after setting a new score, returning to song select after main menu).
	leaderboardManager.FetchWithCriteria(new LeaderboardCriteria(fetchBeatmapInfo, fetchRuleset, Scope.Value, FilterBySelectedMods.Value ? mods.Value.ToArray() : null, fetchSorting), forceRefresh: true);
	if (!initialFetchComplete)
	{
	// only bind this after the first fetch to avoid reading stale scores.
	fetchedScores.BindTo(leaderboardManager.Scores);
	fetchedScores.BindValueChanged(_ => updateScores(), true);
	initialFetchComplete = true;
	}
	}, initialFetchComplete ? 300 : 0);

and because the refetch is thusly delayed, there's a very high chance it will not run before the screen is resumed because the wedge will not have its scheduler run until that point in time.

This conundrum is also why there is no test coverage for this, because the above makes test coverage setup rather annoying.

[peppy]

I guess this is okay for now. (rationale: we don't need to queue this because it always refreshes on mode change).