Adjust minor BeatmapSetOverlay details to better match osu-web

[thewildtree]

Follows #7724, aims to bring the BeatmapSetOverlay even closer to its osu-web counterpart. These changes are mostly small details, but they definitely can affect the UX.

A few things worth noting:

• the scoreboard font size change from mentioned PR has been reversed - while 12 technically matches osu-web, scaling in lazer is a bit different, making 14 bring a more familiar look here
• scoreboard had wrong order of columns just like TopScoreStatisticsSection (as mentioned in #7725), I applied a similar solution, but I'm not sure if it's the proper one here. maybe instead of this we should sort them before they get passed to any UI components?
• added some checks to hide ratings / show placeholder instead of success rate if beatmap has no leaderboard, but I'm not sure if its done the right way
• wanted to add the green colour to the combo if it was the max possible, same as web has, but currently I believe there's no way to check beatmaps maxcombo in this scope

[bdach]

Please use .\InspectCode.ps1 to find stylistic issues instead of relying on CI to spot them for you, and please don't commit code using the github interface. If you're away from an IDE, we'll understand, just let it be for the day.

[thewildtree]

Sorry, I couldn't run InspectCode because of some issues with PowerShell on my PC. Will start doing that as soon as I solve them. Also sorry for the CI-fix commit spam, I'm no longer at my PC and github web edit only allows one file per commit. Yup, sorry. Won't do that again.

[thewildtree]

Removed mentioned parts, will create separate PRs for them later.

[smoogipoo]

In general, always match osu-web sizings

[thewildtree]

size 10 is unreadable due to the font rendering issues

in general, if you take a look at the rest of the overlay, most elements use fonts (or overall dimensions) a few px bigger than web and I followed that direction - it seems correct because matching osu-web 1:1 here looks way more off (I suppose due to some scaling behaviour I can't properly explain) and font sizes like 10px are unreadable due to how lazer renders them in overlays.

currently used font sizes make the overlay look much closer to osu-web than if we used 1:1 font sizes.

[smoogipoo]

Match the font sizes. We can uniformly apply a scale at a later point if needed, inside OsuFont itself.

[thewildtree]

Then we'd have to change every single overlay element / font since they're mostly sized a tad bigger than osu-web.

[smoogipoo]

That's correct.

[thewildtree]

Alright, I'll try to work on it, I'm not sure how that's gonna end up looking though.

[peppy]

It will look fine. All metrics should match (font sizes, widths, paddings, margins). Overall adjustments can be applied later on when we decide how large or small we want things to display.

The important part is that everything matches on a numeric and relative basis so it is easy to confirm correctness without manually pixel checking (aka what you've probably been doing until now).

[thewildtree]

Went back to osu-web font size values as suggested. I'll make a separate PR soon which will aim to bring all the dimensions / sizes 1:1 with osu-web.

[bdach]

I fixed up a few remaining nits; looks fine otherwise.

[bdach]

Think this PR has run its course - I'd say let's get it in for now. Accuracy with web can be iterated on.