🐛 [RUM-3039] Fix missing pending mutations at view end

[amortemousque]

Motivation

We are missing records generated during the VIEW_END lifecycle callbacks (if no segment is already created) because no view is active at that time:

• Miss the pending mutations and view end record
• Miss pending clicks

This PR introduce new BEFORE_XXX lifecycle events where the SDK contexts are still active allowing to send last pending records

Changes

• Introduce new prefixed BEFORE_XXX and AFTER_XXX lifecycle events used by contexts to ensures the context is available during the non prefixed event callbacks.
• Add view related contexts at BEFORE_VIEW_CREATED and close at AFTER_VIEW_ENDED
• Stop the recorder at PAGE_EXITED to prevent unexpected records after the view is closed
• Cleanly stop scrollObserver, moveObserver and instrumentSetter

Testing

• Local
• Staging
• Unit
• End to end

---

I have gone over the contributing documentation.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (ed48184) 92.81% compared to head (b173389) 92.96%.
Report is 8 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2598      +/-   ##
==========================================
+ Coverage   92.81%   92.96%   +0.14%     
==========================================
  Files         236      236              
  Lines        6833     6850      +17     
  Branches     1499     1500       +1     
==========================================
+ Hits         6342     6368      +26     
+ Misses        491      482       -9     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[amortemousque]

/to-staging

[dd-devflow]

🚂 Branch Integration: starting soon, merge in < 0s

Commit b4330d4d71 will soon be integrated into staging-07.

This build is going to start soon! (estimated merge in less than 0s)

Use /to-staging -c to cancel this operation!

[dd-devflow]

🚂 Branch Integration: This commit was successfully integrated

Commit b4330d4d71 has been merged into staging-07 in merge commit 9a0cc04877.

Check out the triggered pipeline on Gitlab 🦊

[amortemousque]

/to-staging

[dd-devflow]

🚂 Branch Integration: starting soon, merge in < 9m

Commit 768b4a46fc will soon be integrated into staging-07.

This build is going to start soon! (estimated merge in less than 9m)

Use /to-staging -c to cancel this operation!

[dd-devflow]

🚨 Branch Integration: The build pipeline contains failing jobs for this merge request

We couldn't automatically merge the commit 768b4a46fc into staging-07.
Build pipeline has failing jobs for 2a4dad1

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected before the end of the pipeline.

You should have a look at the pipeline, wait for the build to finish and investigate the failures.
When you are ready, re-add your pull request to the queue!

⚠️ Do NOT retry failed jobs directly.

They were executed on a temporary branch created by the merge queue. If you retry them, they are going to fail because the branch no longer exists.

If you think the errors come from a logical conflict with the target branch, you can create a fix by commenting this pull request with /create-fix-branch -b staging-07

Details

List of failed jobs:

• check-staging-merge

Go to failed Gitlab pipeline.

If you need support, contact us on Slack #ci-interfaces with those details!