Use browser-native DecompressionStreams

[tuner]

(De)compression streams are now supported in all web browsers: https://developer.mozilla.org/en-US/docs/Web/API/DecompressionStream

Pako is pretty fat and slow. There's also fflate, which is faster and more lightweight, but migrating to that doesn't make much sense now that a native solution is available. Maybe compression streams could be used by default with fallback to pako (at least for now) ?

Context: I was experimenting with tabix & gff-js and there seems to be several optimization opportunities. However, this would probably the most straightforward one, assuming that the native decompression stream is at least as performant as fflate is.

[cmdcolin]

this would be great...would definitely be interested to check if it can handle bgzf, that is one of the tricky parts of our pako code

[cmdcolin]

(note that we have built up some maybe awkward stuff around creating virtual file offsets based ids based on the pako code over time, but we could maybe make new workarounds based on decompression stream also)

[cmdcolin]

this repo has an example of using browser-native DecompressionStream, it is possible it could be used https://github.com/nrminor/genotype/blob/main/src/formats/bam/bgzf.ts#L434-L463

[cmdcolin]

I tried seeing how it might work in this library but the performance results were a bit of a mixed bag, though I didn't try to optimize it much, just did the most basic thing that worked

#70