fix: handle aborted/inflight network requests

[vigneshshanmugam]

• fix DNS failures not represented correctly #246 investigate network events without timing data #190

• We now properly calculate the request timings

  • When the remote host connection cannot be made (Network failure)
  • When the response is never received for a given request
  • When the request in inflight is aborted

• Added test cases for all the scenarios and tested the confirmed the timing with chrome devtools.

When the request is queued and the request got aborted due to browser being explicited closed or the connection cannot be established - The timing data point would look like this explaining that the given request is stalled / blocked for the whole time frame.

{
  blocked: 2.885,
  queueing: -1,
  proxy: -1,
  dns: -1,
  ssl: -1,
  connect: -1,
  send: -1,
  wait: -1,
  receive: -1,
  total: 2.885
}

Matching chrome devtools behaviour

[apmmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Build Cause: Pull request #251 opened

• Start Time: 2021-04-06T23:58:56.581+0000

• Duration: 18 min 53 sec

• Commit: a230fa9

Test stats 🧪

Test	Results
Failed	0
Passed	77
Skipped	0
Total	77

Trends 🧪