New: Added Chrome Traces to cdp connector

[axemclion]

Chrome Traces has much more information about performance and
rules can use the new events - tracing::data and tracing::end
for trace information.

This information can be used for new rules like firstPaint,
total time taken to parseHTML, long frames, rendering, etc.

[jsf-clabot]

All committers have signed the CLA.

[alrra]

@axemclion Thanks for the PR!

Can you sign the CLA? Thanks!

---

Cc: @molant @sarvaje

[panarasi]

Sorry, I think I sent the PR using a wrong account. I work for Microsoft.

[molant]

@panarasi you still need to sign the CLA. The code now belongs to the JS Foundation 😊

[sarvaje]

@panarasi the build is failing because of some eslint errors

[axemclion]

@sarvaje Fixed eslint issues.

[axemclion]

In line 551, I am not using reject since the whole block is wrapped inside a setTimeout anyway. Is that ok ?

[sarvaje]

Can Tracing.end throw an exception? if so, you can wrap it in a try/catch and call to reject in the catch

[axemclion]

I think Tracing.end would throw just as Page.navigate or other chrome commands would. This just sends the command over to chrome over the protocol, so IMHO, it should be fine.

[molant]

Closing this as there's more work that needs to happen to enable it in all connectors but definitely something we want to add in the future.