Add option to tune how the buffer size is allocated.

[gendx]

As mentioned in #22 (comment), there is a trade-off between memory usage and speed.

I suggest adding an option to control the original size of the LZ buffer:

• DictSize would initialize a buffer of the full dictionary's size right away. That's the behavior before Do not allocate buffer size before necessary #22.
• InitialSize(value: usize) would instead initialize it to min(value, dict_size). The behavior after Do not allocate buffer size before necessary #22 is InitialSize(0).

It remains to be seen whether there would be a performance regression between the code before #22 and using the DictSize option.

[dragly]

I think this makes sense. It would be interesting to also see how other libraries handles this. After all, it might be that the files we are parsing are actually malformed and should have reported a smaller dictionary size.

I would be very happy with using DictSize by default if we can override it by setting InitialSize in options.

Also, it would be interesting to know why the allocation is using alloc_zeroed. Perhaps it is possible and safe to use a non-zero-initialized buffer? Our problem was that alloc_zeroed is slow in WebAssembly because of a call to memset.