[JS] Package release script for NPM modules

[asfimport]

Since the NPM JavaScript module may wish to release more frequently than the main Arrow "monorepo", we should create a script to produce signed NPM artifacts to use for voting:

• Update metadata for new version
• Run unit tests
• Create package tarballs with NPM
• GPG sign and create md5 and sha512 checksum files
• Upload to Apache dev SVN

i.e. like https://github.com/apache/arrow/blob/master/dev/release/02-source.sh, but only for JavaScript.

We will also want to write instructions for Arrow developers to verify the tarballs to streamline the release votes

Reporter: Wes McKinney / @wesm
Assignee: Paul Taylor / @trxcllnt

PRs and other links:

• GitHub Pull Request #1346

_{Note: This issue was originally created as ARROW-1577. Please see the migration documentation for further details.}

[asfimport]

Paul Taylor / @trxcllnt:
@wesm does the voting process determine whether the release is published to npm? or should I include the npm publish steps in the release script?

[asfimport]

Wes McKinney / @wesm:
We would wait until the vote passes to publish to npm – the best thing would be for the npm publish step to be possible from the JS source artifact, so that what gets published on NPM is a by-product of the signed tarball that's been approved by the community

[asfimport]

Wes McKinney / @wesm:
We should get this up and running and have a first JS release. Can I help with this?

[asfimport]

Wes McKinney / @wesm:
Issue resolved by pull request 1346
#1346