Limit log monitoring + add more details

[ThibautGeriz]

Motivation

Too much logging in the foregroundContext manager

Changes

• do not log error if two events are coming real close: https://bugs.chromium.org/p/chromium/issues/detail?id=1237904
• add now to extimate the user impact better

[codecov-commenter]

Codecov Report

Merging #990 (442e84b) into main (d0bacdc) will decrease coverage by 0.03%.
The diff coverage is 75.00%.

@@            Coverage Diff             @@
##             main     #990      +/-   ##
==========================================
- Coverage   88.86%   88.83%   -0.04%     
==========================================
  Files          84       84              
  Lines        3908     3913       +5     
  Branches      864      866       +2     
==========================================
+ Hits         3473     3476       +3     
- Misses        435      437       +2     

Impacted Files	Coverage Δ
packages/rum-core/src/domain/foregroundContexts.ts	92.64% <75.00%> (-2.60%)	⬇️

---

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 d0bacdc...442e84b. Read the comment docs.

[bcaudan]

Can you add a comment to explain your limiting strategy?

[ThibautGeriz]

This is because of this chrome bug. It currently dispatches two events separated by ~1ms. I've set it at 10ms to be large & because if our foreground periods are off by 10ms we do not really care.
I also added the now in the log to actually get an insight by how much we're off. I am not really fixing the base issue, just ignoring this chrome bug & adding monitoring info.

[bcaudan]

LGTM