In version 1.x of this library it was possible to call `v4('binary')` in
order to receive a byte array instead of a string representation. This
function signature was deprecated in 2.x (but not removed in 3.x as it
should have been).

The correct way to get a binary representation of a uuid is to pass an
array-like object as a second parameter:

```
const buffer = new Array();
v4(null, buffer);
```

Fixes #437.

Pre-allocate a fixed size array instead of an empty array when no array is passed.

Revert the default parameter introduced in
0ee0b67 since this currently increases
bundlesize in the browser build in does not provide significant benefits
(bable's transpilation is more verbose than our current approach).

Fixes #452.

I no longer want to try to achieve consistent line lengths in markdown
so I'd prefer prettier to do that for me.

Co-authored-by: awwit <ignatius.awwit@gmail.com>

This basically does the opposite of d5ce415

See discussion in #462

Co-authored-by: Guy Bedford <guybedford@gmail.com>

Browserstack seems to have trouble accessing the local proxy on recent
Edge 18.0 / Windows 10 machines. Since Edge 18.0 is deprecated anyways
and since we still have an Edge 15.0 test as a safety net it should be
fine to just drop the Edge 18.0 test.

Thanks to pkg.exports this module is now well-supported by
https://jspm.org/ without any Node.js crypto api polyfills for the
browser.