feat: capture network payloads (internal alpha)

[pauldambra]

rrweb has network payloads queued up as a feature... but it's taking a while.

The easiest way to test it is to adopt it ourselves.

This adds a copy of the plugin proposed for rrweb, and uses it to wrap xhr and fetch.

We can match performance timings and these new NetworkRequests based on URL and timings

used by PostHog/posthog#18562

for now this can only be enabled via decide response, which allows header and body capture to be configured separately

TODO

• this is quite a size bump should we be lazy loading this (and performance observer?)
• what limits should we be applying that we'll regret if we don't?
  • limit on payload size?

[github-actions]

Size Change: +12.9 kB (+2%)

Total Size: 732 kB

Filename	Size	Change
dist/array.full.js	173 kB	+1.1 kB (+1%)
dist/array.js	115 kB	+1.09 kB (+1%)
dist/es.js	115 kB	+1.09 kB (+1%)
dist/module.js	115 kB	+1.09 kB (+1%)
dist/recorder-v2.js	104 kB	+8.58 kB (+9%)	🔍

ℹ️ View Unchanged

Filename	Size
dist/exception-autocapture.js	12 kB
dist/recorder.js	58.3 kB
dist/surveys.js	39.8 kB

_{compressed-size-action}

[benjackwhite]

Should we move all of this stuff (aside from maybe some types) into the recorder loader?

[benjackwhite]

This looks great and is very exciting.

Only thing I'm wondering is if we sadly need an additional remote config flag for this, otherwise we will immediately start capturing request and response data for all existing people who have perf enabled...

[benjackwhite]

Lets goooo