✨ [RUMF-770] Disable tracing for cancelled requests

[webNeat]

Motivation

Do not trace cancelled requests because they lack backend information.

Changes

Set request.traceId to undefined if the request was cancelled.

Testing

Added unit tests to ensure that traceId is removed from the LifeCycleEventType.REQUEST_COMPLETED event when the request.status == 0.

---

I have gone over the contributing documentation.

[codecov-io]

Codecov Report

Merging #635 (428c510) into master (f8c339b) will increase coverage by 0.15%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #635      +/-   ##
==========================================
+ Coverage   87.78%   87.93%   +0.15%     
==========================================
  Files          56       56              
  Lines        2578     2577       -1     
  Branches      556      555       -1     
==========================================
+ Hits         2263     2266       +3     
+ Misses        315      311       -4     

Impacted Files	Coverage Δ
packages/rum/src/domain/requestCollection.ts	87.87% <100.00%> (+9.50%)	⬆️
packages/rum/src/domain/tracing/tracer.ts	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f8c339b...428c510. Read the comment docs.

[bcaudan]

👍

[buenjybar]

Hi guys,

I was trying out the latest version of today the lib ( 2.2.1 ) and,
Unfortunately, I can still see some errors related to "canceled XHR requests"

XHR error GET https://URL/..
It is happening on both LOG and RUM libs

attached some screenshots

1. 
2. 

[BenoitZugmeyer]

This is expected. This PR disables traces for those requests, but they are still considered as errors. Could you provide more information about your issue/use-case?

[buenjybar]

Ok,
I understand you will still log them as an error, and it is ok since you are following HTTP error standards, here
This can bring some confusion to the support team when investigating bugs, ( I could add a pipeline to downgrade this error code:0 to Warnings level )
People think it is a legit HTTP error but it is actually part of our code ( we cancel the request and trigger a new one)