Prepare for npm publish and also reworking the cryptoworker and additional tests

[robert-cronin]

This is to prepare and eventually do npm publish
Fixes #16

[CMCDragonkai]

I think to go through the crypto code we would need to have a meeting. It would be difficult for me to review it on my own.

[robert-cronin]

I think to go through the crypto code we would need to have a meeting. It would be difficult for me to review it on my own.

I agree, there is quite a bit to go through here, let me know when is best 👍

[CMCDragonkai]

Main thing is to add as much fuzzing tests to the readSync/writeSync functions because they are really complex.

One way to do this is to check synchronous behaviour "bisimulation" between real fs and EFS when seeking randomly and reading randomly and writing randomly. And comparing the pre and post conditions.

Just a note to write down, page cache for read hasn't been implemented, whereas page cache has been implemented for "write then read". For read, it requires us to figure out the chunk mapping index structure because we need to keep track of "true nulls" vs nulls of convenience ("non-existent nulls").

[robert-cronin]

I've added quite a few bisimulation tests that test all the way from 1-3 blocks, 1-2 rounds of read/write as well as bisimulation tests for readFileSync and writeFileSync.

[CMCDragonkai]

Ok I'm merging this.