fix: getNumber varint decode bug

[JonasKruckenberg]

This hopefully fixes #50 by removing the call to numberToUint8Array() in varintUint8ArrayDecode.
It returned a wrongly encoded Uint8Array that had 1 as it's first byte, so all codec above 256 could not be resolved.

[vmx]

Thanks for your contribution, fixing this very long lasting bug. Please see my comment for even less code.

[JonasKruckenberg]

Should all be resolved.

[hacdias]

Hey @JonasKruckenberg! It LGTM. Could you just fix the linting issues as well as squashing the commits into one using the conventional message format so we can have CI running?

[vmx]

You can run linting locally via npm run lint.

[JonasKruckenberg]

Alright, I had to do more rebase magic that I expected, but now things should be nice and tidy. The failing coverage test is nothing I can fix right? Because it seems like it's complaining just because I removed code.

[vmx]

@JonasKruckenberg Thanks a lot of the hard work and reworking everything so that it conforms to our CI stuff (yes you can ignore that codecov error).

In case you still feel like polishing, your commit message has typo: "deocde" -> "decode".

[JonasKruckenberg]

Thanks hahaha, I didn't notice that, I also spelled it wrong twice in the same commit.
Anyway, it was a pleasure!
Cheers