🐛 allow 1 ms error for matching request

[bcaudan]

Motivation

Flaky e2e tests put in evidence that timing associated to an instrumented request can not alway be perfectly nested.
Observed case:

Req start     593.3949999
Timing start  593.5950000
Req end       799.3949999
Timing end    799.5550000

Changes

Allow a 1 ms error margin in the matching condition.

Testing

unit + ci

---

I have gone over the contributing documentation.

[codecov-commenter]

Codecov Report

Merging #824 (5470b2f) into master (cf5109a) will decrease coverage by 0.15%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #824      +/-   ##
==========================================
- Coverage   86.87%   86.72%   -0.16%     
==========================================
  Files          80       80              
  Lines        3871     3872       +1     
  Branches      879      879              
==========================================
- Hits         3363     3358       -5     
- Misses        508      514       +6     

Impacted Files	Coverage Δ
...rumEventsCollection/resource/matchRequestTiming.ts	95.45% <100.00%> (+0.21%)	⬆️
packages/rum-core/src/transport/batch.ts	62.85% <0.00%> (-11.43%)	⬇️
packages/rum-core/src/domain/parentContexts.ts	98.24% <0.00%> (-1.76%)	⬇️
...ckages/core/src/domain/automaticErrorCollection.ts	98.59% <0.00%> (-1.41%)	⬇️

---

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 cf5109a...5470b2f. Read the comment docs.