fix: put RemoteCertVerifier upstream from the caching and coalescing layers

[nornagon]

Description of Change

This fixes #28313.

Before this change, the RemoteCertVerifier would receive several concurrent
requests to verify the same domain, and the 2nd one to return would cause a
crash. I'm not totally sure what the exact cause of the crash was, but putting
the RemoteCertVerifier upstream from the coalescing and caching layers means
that only one verification request gets sent to the main process, and by doing
so fixes the crash.

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• tests 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 a network process crash that could happen when using setCertificateVerifyProc with many concurrent verification requests.

[release-clerk]

Release Notes Persisted

Fixed a network process crash that could happen when using setCertificateVerifyProc with many concurrent verification requests.

[trop]

I was unable to backport this PR to "12-x-y" cleanly;
you will need to perform this backport manually.

[trop]

I was unable to backport this PR to "11-x-y" cleanly;
you will need to perform this backport manually.

[trop]

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

[trop]

@nornagon has manually backported this PR to "12-x-y", please check out #28465

[trop]

@nornagon has manually backported this PR to "11-x-y", please check out #28470