gh-152433: Windows: Allow build winreg module for UWP

[thexai]

In current code, winreg module is not build because code guards not include MS_WINDOWS_APP.

Instead of add MS_WINDOWS_APP condition, guards removed when is:

#if defined(MS_WINDOWS_DESKTOP) || defined(MS_WINDOWS_SYSTEM) || defined(MS_WINDOWS_GAMES)

(as includes all Windows families)

Or replaced with MS_WINDOWS when code is for all platforms.

The clinic's code also regenerated, resulting in the removal of many redundant conditions.

Note that Windows Registry is not accessible from UWP Apps (or Games) but for consistency is necessary build module as is imported in many places at Python initialization. The same logic was already being applied with MS_WINDOWS_GAMES build.

• Issue: Windows: improve compatibility to build for UWP / Xbox #152433

[zooba]

Out of interest, what would it look like to make those imports conditional? They ought to be anyway, and I suspect we'll end up with better overall behaviour if they handle this as "no registry access exists" rather than "registry accesses always fail".

[thexai]

I don't really know how it would be done because it requires modifying a lot of Python code and introduce helper functions or constants to identify UWP / GAMES builds as "another platform". This is beyond the scope of this PR.

In addition to this, I want to avoid modifying the behavior of MS_WINDOWS_GAMES builds because I have no easy way to test it (nor any particular interest).

This PR allows compile the current code for UWP and is actually a simplification because it removes 185 lines of code. Without this PR, the resulting UWP builds won't work because they try to import a module that doesn't exist --> hard crash.

With this PR, you can use the rest of the Python code in UWP, and even if a Python script includes import winreg lines and the the script handles the exceptions, return values, etc. nothing bad happens.

Previously, Windows Registry was available for "Windows Phone" in the MS_WINDOWS_APP partition, and most of the Win32 Registry API is still defined. This is why compile winreg.c code for MS_WINDOWS_APP/GAMES is possible and doesn't produce errors. I'm not actually sure if accessing the Registry outside of classic Desktop environment is still useful on other types of devices (Surface or ARM64 devices).

[zooba]

Having had a quick look, it seems like Lib\importlib\_bootstrap_external.py is the only one that needs handling. getpath.py and the rest of the standard library uses are protected (apart from one in IDLE, which I assume you don't care about).

Some of the test suite also assumes the module will be there, and those ought to be handled either at the winreg import or the command importing the module that requires it.

There's no need to modify anything conditionally on the build, it's just going to be something like:

try:
    import winreg
except ImportError:
    winreg = None

...

if winreg:
    # do the thing requiring the registry
else:
    # fallback behaviour if needed

For _bootstrap_external.py I think it's just an entire block that's already optional for non-Windows, so that can become for non-winreg, and it should be good.