Add better support for LZW

[manzt]

I experimented with porting a pure Rust implementation of LZW to WASM: lzw-tiff-decoder. The bundle is kind of large (~50kb) but it's quick and sufficient for loading the default raw2ometiff output.

Ideally we could add the decoder to our code base under viv's getDecoder, but I had to make really minor changes to geotiff.js to support swapping a new wasm module. I opened an issue in geotiff a few days ago (geotiffjs/geotiff.js#172) related to making these changes.

I'm not sure if they will be open to the new decoder since it is large in comparison, but for something like avivator it would be really nice. Ideally we could code split the javascript/wasm for each decoder and only fetch when presented an image with a certain decoding.

[ilan-gold]

@manzt I hadn't realized this wasn't merged yet - do you want to merge this? I have LZW data generated for benchmarking if you'd like to benchmark the compression used as well. It could be interesting.

[manzt]

I opened an issue in geotiff (which needs a better name now): geotiffjs/geotiff.js#172,
but essentially I'd hope that consumers could define their own decoders without "paying the price" for all the built-ins.

I'm happy to move forward however, because the changes on my fork are fairly minimal and it adds better support for LZW.

[ilan-gold]

This is the branch I was referring to - https://github.com/ilan-gold/geotiff.js/tree/ilan-gold/viv_050_release

It has both AbortController and the async-ify + LZW changes.