Explore Electron.net API support in the utility process

[deepak1556]

It would provide us with the possibility of using chromium network stack which has better support for proxies directly from the utility process. Currently chromium transfers URLLoaderFactories to renderer process which allows blink to make network requests directly from the network service without having the need to go through the browser process, we will try to follow the same principle in this exploration.

• Validate the exploration using a simple prototype
• Scaffold Electron.net for the utility process

Prototype Implementation:

Let's create a interface on the NodeService utility process which accepts a URLLoaderFactory from the browser process and uses it to create a URLLoader to issue simple http(s) requests and outputs the response to a file.

Consists of 3 components

• Declaring a mojo interface to transfer the URLLoaderFactory
• Defining the interface in the Utility Process
• Invoking the interface from the Browser Process

/cc @devm33

[deepak1556]

/fixedWith #202053

[deepak1556]

Steps for verification:

• Add the following setting "github.copilot.advanced": { "debug.useElectronFetcher": true }
• Reload Window
• Open Github Copilot Chat output panel and check for the following log FetcherService] Using Electron fetcher
• Test that chat requests are fullfilled without any network issues.

[joaomoreno]