Prepare release scripts

[kou]

What's Changed

This is based on the release scripts used by apache/arrow-java:
https://github.com/apache/arrow-java/tree/main/dev/release

Here is the release workflow:

1. Bump version in package.json
2. Run dev/release/release_rc.sh 1
   1. This push vX.Y.Z-rc1 tag
   2. The tag push runs GitHub Actions workflow for RC that:
      1. Generates source archive and packages for https://www.npmjs.com/
      2. Verifies these artifacts
      3. Creates a GitHub Release for the RC and uploads these artifacts to the GitHub Release
   3. This downloads these artifacts from the GitHub Release
   4. This signs these artifacts on local and upload these signs to the GitHub Release
   5. This shows vote e-mail template
3. Start a vote on [email protected]
4. Run dev/release/release.sh 1 after the vote carried
   1. This push vX.Y.Ztag
   2. The tag push runs GitHub Actions workflow for release that:
      1. Creates a GitHub Release for the release and copies all artifacts from the GitHub Release for the RC
   3. This uploads the voted source archive to https://dist.apache.org/repos/dist/release/arrow/
   4. This removes old releases from https://dist.apache.org/repos/dist/release/arrow/
   5. This publishes the voted packages to https://www.npmjs.com/
5. Add the release to ASF's report database: https://reporter.apache.org/addrelease.html?arrow

See also the added dev/release/README.md.

Closes #9.

[kou]

I tried this workflow on my fork:

• RC workflow: https://github.com/kou/arrow-js/actions/runs/15431752994
• RC GitHub Release: https://github.com/kou/arrow-js/releases/tag/v20.0.0-rc2
• Release workflow: https://github.com/kou/arrow-js/actions/runs/15432429380
• Release GitHub Release: https://github.com/kou/arrow-js/releases/tag/v20.0.0

[kou]

I'll merge this in a few days if nobody objects it.

[raulcd]

Sorry @kou I haven't had much time to go through it.
In general looks good to me, I have a question about the npm publishing and having the possibility to retry it.
We can also add that functionality of retrying npm as a separate PR or an improvement if you think is best.

[raulcd]

should we have an option to only publish to npm and avoid the rest?
I've had to retry the publishing npm script in the past due to timeouts our random failures with OTP login and seems worth to me.
Either that or split this in a two steps process?

[kou]

It makes sense. I've added RELEASE_* environment variables.

[kou]

No problem. Thanks for your review!

[kou]

I'll merge this.