ref(replay): Use fflate instead of pako for compression (#9436)

According to their own benchmarks
(https://www.npmjs.com/package/fflate), this should be faster, and have
a smaller bundle size.

We still use pako in integration tests, to verify this is stable (for
now) - we can eventually also move this to fflate.
We also have E2E tests that should also verify that this still works as
expected.

Author: mydea

packages/browser-integration-tests/package.json

@@ -59,6 +59,7 @@
   "devDependencies": {
     "@types/glob": "8.0.0",
     "@types/node": "^14.6.4",
+    "@types/pako": "^2.0.0",
     "glob": "8.0.3"
   },
   "volta": {

packages/browser-integration-tests/suites/replay/compression/init.js renamed to packages/browser-integration-tests/suites/replay/compressionEnabled/init.js

@@ -10,3 +10,9 @@ This is an internal package that is used by @sentry/replay.
 It generates a web worker and converts it to a string, so that we can process it easier in replay.
 
 By extracting this into a dedicated (private, internal) package, we can streamline the build of replay.
+
+## Example Worker
+
+You can find an example worker for if you want to self-host the compression worker in [/examples](./examples/).
+
+This is generated from the actual soure via `yarn build:examples`, which should be run manually whenever replay-worker is updated.