fix: update readSync to not provide seek / offset parameters

[trgwii]

Something in the internals of fs.readSync changed at some point, which causes the following error if you provide an offset integer to readSync while reading stdin:
ESPIPE: invalid seek, read
Solution is to not provide additional arguments, as the defaults are equivalent for this usecase.
Tested on Debian 11 and Windows 10

Closes #158

[uncenter]

I mean the defaults don't look equivalent; 0, 1, 0 vs 0, buf.byteLength, null. This does fix my issue but I want to make sure this won't break other things :)

[trgwii]

Unless this breaks on macOS, I don't think there are other cases to consider, as readlineSync is only used by the prompt / confirm builtins, the only usecase is synchronously fetching an answer from a user on stdin.

[uncenter]

Working for me on macOS!

[uncenter]

Any update on this and #160? Both look good to merge to me.

[trgwii]

For the record, this should be a nonbreaking change for older node versions as well, since I just omit optional parameters here.

[dsherret]

LGTM. Thanks! I will merge this tomorrow along with the other PRs then do a release then.