Update rrweb to version 2.x

[Lms24]

Problem Statement

While our Replay integration is still in beta, we'd like to look into updating rrweb to version 2.x, thereby avoiding potentially breaking changes in a future stable state. Furthermore, v2 might improve certain aspects of rrweb, such as 3rd party iFrames (#6560).

Solution Brainstorm

Unfortunately, 2.x is still in an alpha state and development seems to be rather slow. However, we can still start with the update as we vendor a specific rrweb version anyway. This means we have full control over bumping to new 2.x alpha/beta/stable versions in the future.

Problems:

rrweb doesn't provide a migration guide or any information on breaking changes. I'm afraid, we'll need to test all our supported options and check that things still work as intended.

[billyvg]

Yeah I think we should look into v2 regardless of #6560, let me know if you want me to help test.

[Lms24]

Bundle size impact:

According to bundlephobia, rrweb 2.x is a roughly 25% increase in bundle size, compared to version 1.1.3. This raises the question if it's worth taking this hit over e.g. forking 1.1.3 and building/cherry-picking from there.

[Lms24]

Closing this as I don't think we're gonna tackle this any time soon. We can re-open if it comes up again.

[Lms24]

Whenever we look at this, one compelling reason to upgrade is rrweb-io/rrweb#1107 (whenever it gets merged)