Fix gameplay skipping forward during resume operation

[peppy]

Closes #19975.

I'm not precisely sure where this regressed in the changes, but it did. Rather than trying to figure out where the issue lies, I've just explicitly added this flow so we are aware of what is going on where and when.

Inline comment should explain this quite well.

[frenzibyte]

I've took the time to debug through why this is occurring with the refactor and it turns out this is how things are supposed to work w.r.t. pause and resume:

1. GameplayClock.Stop() is called due to user pause, setting IsPaused.Value = true and transforming the frequency to zero
2. While the frequency is being adjusted, the clocks stop getting processed on Update
3. GameplayClock.Start() is called due to user resume, seeking the track to the last processed frame time, which was at the moment Stop() was called.

This led to the realisation that FramedBeatmapClock actually always calls ProcessFrame regardless of the paused state, unlike the previous GameplayClockContainer version which processes the clocks only when in running state:

So while the solution here is valid, the new behaviour with FramedBeatmapClock makes me feel slightly uneasy about it potentially regressing other scenarios, but I can't think of any in my head, so we'll see how things go.

[frenzibyte]

Also there seems to be leftover/debugging changes pushed in this PR.

[frenzibyte]

As per my comment above, this is now pretty much pointless since the clock is always processed regardless of pause state.

[peppy]

I've removed this for now.

[peppy]

I figured that's how things were, although for whatever reason couldn't find the code in your screenshot.