chore: add snapshot release workflow

[ShookLyngs]

Changes

• Add a GitHub workflow to release packages' snapshot, which performs the following tasks:
  1. Releases snapshots for every commit to the main or develop branch
  2. Creates a comment on the commit if snapshots was released

Request review

@Flouse @Dawn-githup Can you help review the process of the workflow?

[duanyytop]

Do we need releases so frequently?

JoyID should only use the BTC transfer function and display the BTC balance, and the CKB package only needs internal references and does not need to rely on npmjs package.

I suggest setting the develop as the default branch and only releasing when the pull requests are merged to the main branch.

[Flouse]

Do we need releases so frequently?

Yes, frequent releases may not be necessary.

I suggest setting the develop as the default branch and only releasing when the pull requests are merged to the main branch.

Agree with that.

[Flouse]

After discussing with @ShookLyngs ,
we think it doesn't hurt to release frequently if there is a tag mechanism clearly visible at the top of NPM package version page.
e.g. https://www.npmjs.com/package/@ckb-lumos/lumos?activeTab=versions

And the snapshot versions are convenient for testing.

So, let's merge this PR and focus on the new features.