fix: integration test opting out

[pauldambra]

@neilkakkar and I were answering questions about what the library does if started in opted out state

Things are complicated enough that it's hard to read the code and be sure we're giving good advice

It turns out that if you opt out we drop messages at capture, so even if areas of posthog-js start running they can't send events.

But that also means that for e.g. we lazy load the entire JS bundle, track DOM mutations, and then drop any snapshot events.

We should not start session recording until we're asked to...

This PR:

• adds integration tests for session recording opted out state
• doesn't download the recorder bundle when opted out
• removes given from Cypress tests
• converts Cypress tests to typescript

[github-actions]

Size Change: +464 B (0%)

Total Size: 758 kB

Filename	Size	Change
dist/array.full.js	178 kB	+116 B (0%)
dist/array.js	119 kB	+116 B (0%)
dist/es.js	119 kB	+116 B (0%)
dist/module.js	119 kB	+116 B (0%)

ℹ️ View Unchanged

Filename	Size
dist/exception-autocapture.js	12 kB
dist/recorder-v2.js	104 kB
dist/recorder.js	58.4 kB
dist/surveys.js	48.7 kB

_{compressed-size-action}

[marandaneto]

FWIW Android does the same, Replay calls capture always, and then capture checks the optOut flag and bails out if needed.

We should not start session recording until we're asked to...

Android is different because you can only hook up early in the app lifecycle (using the AppContext), so we have to hook up to the observers and not capture anything when it's triggered, it's less overhead than observing everything but more overhead than not doing anything.