fix: revert to legacyMainResolve in JavaScript for asar compatibility

[VerteDinde]

Description of Change

Addresses #41241

Node's recent upstream conversion of legacyMainResolve from JavaScript to C++ (nodejs/node#48325) unfortunately doesn't take asar files into account, and may either incorrectly load or entirely fail to find and load the main file if an app is using a combination of ESM and asar, and one of the dependencies is using CommonJS. This PR reverts the native code change while we determine how to patch Node's new methods using asar.

Note: This revert was submitted in place of a potentially riskier fix for Electron's 29 stable release date. I targeted both main and 29-x-y in order to avoid main/branch drift, but happy to target this at 29-x-y only if we'd prefer that.

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• tests are changed or added
• relevant documentation, tutorials, templates and examples are changed or added
• PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.

Release Notes

Notes: Fixed an issue where some dependencies using CommonJS would cause ESM apps to fail to open.

[codebytere]

Supersedes #41348 - we're going to try a better long-term performant fix for 30 and fix it via revert for now.

[release-clerk]

Release Notes Persisted

Fixed an issue where some dependencies using CommonJS would cause ESM apps to fail to open.

[trop]

I have automatically backported this PR to "29-x-y", please check out #41371