Electron Releases

Description of Change

Two of our Node patches only exist to change what native module builds see in common.gypi on macOS: clang=1 (so node-gyp picks the clang/libc++/C++20 xcode settings) and MACOSX_DEPLOYMENT_TARGET=13.0 (#49691, upstream moved to 13.5 while Chromium still supports 13.0). Both values can be expressed from the config.gypi Electron already generates and ships next to common.gypi in the headers tarball, so this moves them there and drops the patches.

• script/generate-config-gypi.py adds ['OS=="mac"', {'clang%': 1}] to variables.conditions (same form the patch used inside common.gypi) and a target_defaults.target_conditions entry for the deployment target; target_conditions evaluate after common.gypi's own conditions, so 13.0 wins over upstream's 13.5.
• The file is now written with json.dumps instead of pprint: node-gyp reads config.gypi by swapping quote characters before JSON.parse, and only the JSON form round-trips condition strings containing "mac". tools/install.py's ast.literal_eval reads it unchanged.
• Verified by evaluating a trivial binding.gyp with node-gyp 12's addon.gypi, upstream's unpatched common.gypi and the new config.gypi (after node-gyp's parse/rewrite) for OS=mac|linux|win: the resulting target dicts match today's patched common.gypi (gnu++20/libc++ xcode settings and 13.0 on mac, no ClangCL toolset on win, nothing on linux).

Checklist

• I have built and tested this change
• I have filled out the PR description
• I have reviewed and verified the changes

Release Notes

Notes: none