fix: revert os_crypt async cookie provider implementation

[VerteDinde]

Description of Change

Follow up to #49371
Fixes #49383

M144 changed the default cookie encryption and cookie provider logic to use OS_Crypt Async, rather than Sync. Originally, we had landed PRs to add new cookie providers cross-platform, following Chrome's upstream implementation. However, we will need to land additional async logic changes to match the new providers, which will be a larger refactor/chunk of work than simply plumbing through to the providers. See #49054 for what that work might look like.

In lieu of that, we've decided to revert the breaking sync -> async change for Chrome M144/Electron 40, in order to ensure compatibility while we make the needed changes. This PR patches out that change - this patch can be removed when the new work lands, targeting Electron 41. This PR also reverts two previous fix forwards that no longer apply.

Fix can be tested using this test repo: https://github.com/VerteDinde/cookie-encryption-test

Note: The revert was pulled from this upstream tracking issue. Please review the changes carefully: https://issues.chromium.org/issues/447372315

Checklist

• PR description included
• npm test passes
• tests are changed or added
• relevant API documentation, tutorials, and examples are updated and follow the documentation style guide
• PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.

Release Notes

Notes: Fixed the cookie encryption logic to use the old os_crypt sync implementation present in M142

[clavin]

Looks great, thanks for fixing this!!

I found no other changes depend on this one in a quick search. Fast-tracking for E40 stable release.

[release-clerk]

Release Notes Persisted

Fixed the cookie encryption logic to use the old os_crypt sync implementation present in M142

[trop]

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