Clean up SCREEN_INFORMATION even further

[lhecker]

A continuation of #19645. Maintainer modifications were disabled, unfortunately.

[lhecker]

[DHowett]

hey, there's nothing wrong with type name{ value } syntax :(

[lhecker]

There's many arguments that can be made against {}. For instance, anything that compiles with = means that initialization is implicit. Assuming no one wrote a non-trivial non-explicit object constructor, this further implies that seeing = means that it's definitely trivial (not just implicit), and that {} is potentially non-trivial and should raise an eye-brow).

That of course excludes things such as default constructors that are non-trivial such as cppwinrt's which allocate an object to avoid "null"s (BAH! I mean it's nice, but BAH!).

[DHowett]

but also, why

[lhecker]

I mean the SCREEN_INFORMATION class is a disgrace no matter how you look at it. #19645 was also kind of meh, because it brought no real benefit. To make things right, this PR at least brings some real improvement: It groups the class methods by their use. This makes it easy in the future to find related functions at a glance (not always obvious given their name), and to clean up the class (because now all of the window methods are grouped together, for instance).