Electron Releases

Follow-up to #53447, found on its 42/43/44 backports (#53568 #53569 #53570), where the Windows clang-tidy job failed with multiple rules generates .tidy.

• GN's compile-commands writer puts a space before every substituted path, so a toolchain command written /Fo{{output}} lands in compile_commands.json as /Fo obj/x.obj. Chromium's Windows cc/cxx tools used that form until 155 changed them to /Fo$output (a plain string, so /Foobj/x.obj). gen-clang-tidy-ninja.py only handled the joined form; with the spaced one every clang-cl entry parsed to an empty object path and every step got the output .tidy.
• Accept both forms, and exit naming the source file if an entry has no object path at all rather than writing a broken ninja file.
• No effect on main today (155 uses the joined form); this keeps main and the release branches on the same script and guards against the toolchain string changing again.

Notes: none