[FIX] Cap Score Displays to their biggest possible values

[JustKolosaki]

Does this PR close any issues? If so, link them below.

3631

Briefly describe the issue(s) fixed.

No, this does not cap the score itself as well. Just wanted to clarify that.
Caps the score displays in ResultState and FreeplayState to their maximum possible value. Adding more numbers instead would just make it look ugly and yucky :[

(this is not as massive of a change as it shows lol it makes it look like the automatically made spaces from vscode settings are one of the changes lol)

[Hundrec]

mmyes
Thank you for preventing another crash!

[JustKolosaki]

mmyes Thank you for preventing another crash!

anytime

[Shaunyman]

The people deserve to have their hundred-million scores displayed! Lol, I'm just messing around. While I would like that to be the case, I'm honestly just glad somebody looked into the issue. If both the freeplay score and the results screen score were capped to 9,999,999, that would fix the crash that happens when trying to select the chart difficulty again, right? Because that's really the biggest issue in my humble opinion.

[JustKolosaki]

The people deserve to have their hundred-million scores displayed! Lol, I'm just messing around. While I would like that to be the case, I'm honestly just glad somebody looked into the issue. If both the freeplay score and the results screen score were capped to 9,999,999, that would fix the crash that happens when trying to select the chart difficulty again, right? Because that's really the biggest issue in my humble opinion.

Yup, that should be why the crash happens - the game tries to reference a null object when the score is over the cap. ResultState is in a similar boat