<!--  As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->

### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->

* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

### Issue Details

* **Electron Version:**
  * 4, 5, 6 
* **Operating System:**
  * not related

* **Last Known Working Electron version:**:
  * doesn't work at all

### Expected Behavior
<!-- A clear and concise description of what you expected to happen. -->
Electron's network request honor NEL header and make NEL request.

### Actual Behavior
<!-- A clear and concise description of what actually happened. -->
Does not happens

### To Reproduce
<!--
Your best chance of getting this bug looked at quickly is to provide a REPOSITORY that can be cloned and run.
-->
Navigate known NEL-enabled endpoint (i.e https://dcreager.net/nel/intro/), collect netlog and check `Reporting` section.

<!--
You can fork electron-quick-start (https://github.com/electron/electron-quick-start) and include a link to the branch with your changes.
-->

<!--
If you provide a URL, please list the commands required to clone/setup/run your repo e.g.
```sh
$ git clone $YOUR_URL -b $BRANCH
$ npm install
$ npm start || electron .
```
-->

### Screenshots
<!-- If applicable, add screenshots to help explain your problem. -->

### Additional Information
<!-- Add any other context about the problem here. -->

NEL (https://www.w3.org/TR/network-error-logging/) is enabled by default from M69 (https://www.chromestatus.com/features/5391249376804864), but in our desktop client based on v4 (and v5, 6 for verification purpose) doesn't honor NEL header so we are not able to collect users using desktop client.

In chromium visiting NEL configured endpoint will make proper NEL request to specified endpoint, and client side behavior can be verified via netlog like below:

![image](https://user-images.githubusercontent.com/1210596/57558111-5ea56480-7331-11e9-99ba-e0d89703b5bd.png)

In Electron, some version simply doesn't have `Reporting` section at all, or if exists it says it's disabled:

![image](https://user-images.githubusercontent.com/1210596/57558135-7381f800-7331-11e9-9ab4-7d463038246a.png)


atom/browser/net/atom_network_delegate.cc
switch (type) {
    case content::ResourceType::kMainFrame:
      return "mainFrame";
    case content::ResourceType::kSubFrame:
      return "subFrame";
    case content::ResourceType::kStylesheet:
      return "stylesheet";
    case content::ResourceType::kScript:
      return "script";
    case content::ResourceType::kImage:
      return "image";
    case content::ResourceType::kObject:
      return "object";
    case content::ResourceType::kXhr:
      return "xhr";
    default:
      return "other";
  }
}
int32_t GetWebContentsID(int process_id, int frame_id) {