fix: move FirstPartySets initialization into the browser process

[VerteDinde]

Description of Change

In this CL, First Party Sets initialization was moved to the content layer: https://chromium-review.googlesource.com/c/chromium/src/+/3448551 . We still need to initialize an empty sets file within Electron's equivalent PreMainMessageLoopRun method. However, our First Party Set initialization is currently in the wrong place.

This PR moves Electron's First Party Sets initialization to the PreMainMessageLoopRun method.

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• tests are changed or added
• relevant documentation is 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 the initialization of first party sets in the browser process.

[deepak1556]

Do we also need to provide a persist storage for FPS https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/chrome_content_browser_client.cc;l=3792-3797 ?

[MarshallOfSound]

@deepak1556 I don't believe so, currently the only way we have to set FPS is via command line flags. If we use a way to set FPS via other //content APIs we'll probably have to set up persistence 👍

[release-clerk]

Release Notes Persisted

Fixed the initialization of first party sets in the browser process.

[trop]

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