chore: Ship unminified file as ESM entrypoint

[zashraf1985]

Background

This PR is copied from 484. It was contributed by @jasonkarns a couple of years ago. I just pulled his changes, merged master and resolved conflicts.

Summary

ESM entrypoints are very very likely to be consumed by bundlers, not loaded directly into browsers. Therefore it is preferable that the bundlers have access to the unminified source so that consumers can have more control over the final output.

This change adds an ESM output bundle that is not minified with terser. (#477 has merged which also adds the unminified ES bundle, so this PR now just makes the unminified bundle the module entrypoint.)
Notably, the unminified bundle is created in addition to the minified bundle;
so the minified bundle is still distributed with the package (at the same output location).

This way users who do actually want the minified bundle may still use it.

However, the package.json#module entrypoint is changed to reference the unminified bundle, as this is most likely what users will want when consuming from a bundler. (And bundlers are virtually the exclusive consumers of the module entrypoint.)

[coveralls]

Coverage remained the same at 97.185% when pulling 4f00c9e on zeeshan/change-module-entry into 5e8d539 on master.

[coveralls]

Coverage remained the same at 97.185% when pulling 4f00c9e on zeeshan/change-module-entry into 5e8d539 on master.

[msohailhussain]

lgtm