Fix missing remote object error when calling remote function created in preload script

[zcbenz]

Description of Change

Previously we were using sender.getProcessId() to determine whether the context of a remote function still lives. But since sender.getProcessId() may still return the ID of previous page when the new page is still loading, we will wrongly report "missing remote object error" when the remote function is created in preload script.

This PR removes the check of sender.getProcessId() in the main process, and instead checks the contextId in the renderer process which is reliable.

Close #14965.

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• tests are changed or added

Release Notes

Notes: Fix missing remote object error when calling remote function created in preload script

[zcbenz]

Manually backported as in above links.

[MarshallOfSound]

@zcbenz There is a consistent test failure here

ipc renderer module remote listeners detaches listeners subscribed to destroyed renderers, and shows a warning - detaches listeners subscribed to destroyed renderers, and shows a warning

[zcbenz]

I have fixed the failing test.

There is a slight change that, the warning is now printed asynchronously after the renderer process checked the contextId and reported back to the main process. This is because we don't have a reliable way to know whether a remote function still lives in the main process, we have to explicitly ask the renderer process.

[codebytere]

nit: preload: preload can just be preload

[jkleinsc]

LGTM

[release-clerk]

Release Notes Persisted

Fix missing remote object error when calling remote function created in preload script

[jjcm]

Thanks for this fix @zcbenz and props for the quick review @codebytere and @jkleinsc ! This fix really helps me out :) 👍