fix: performance on node

[ThaUnknown]

This PR fixes a performance issue when using Transform streams, which caused some video players to get stalled, this was because the transform would wait for the parser to finish parsing before it could continue, we don't care about that as we don't mutate data, just parse it

Additionally it fixes an issue where subtitlestream would stop parsing it metadata wasn't fully according to spec, for example some encoders would embed CR32 as the first tag in the cluster, not the timescale

Adds chapters

[mathiasvr]

How do you detect data loss? Do you get any exceptions? I'm not sure how to reproduce.
I'm seeing that the emit event can delay data but it's still the same chunks and in the same order as the transform method.

[ThaUnknown]

No errors get thrown, but 1/2 of the chunks pushed to the stream are ignored by the transform for some reason, tends to happen on chunks of constant sizes which come in very slowly.

The way I detected data loss is I summed the data being pushed and data being received and it was exactly half, however this might have been an issue caused by electron's node integration, rather than node itself, this definitely fixed it however, reproducing is a bitch however.

This happened with webtorrent's file.createReadStream which seems compliant with node's readable streams.

[mathiasvr]

The only thing I can think of is that there could be an issue with the way the previous instance is closed (when seeking to new offset), however since the transform method gets called before the data event it doesn't make sense that it could fix data loss?

It would be great if you could come up with some not too complicated reproduction to better understand what the issue is, but otherwise I will just do some testing later to check that the 'data' event works for other cases.

[ThaUnknown]

@mathiasvr I've updated this PR