Preparing for the ASF release

[Xuanwo]

Our release workflow needs to be refactored to comply with the ASF release process requirements. Unlike OpenDAL, reqisn is a project composed of many sub-crates.

So I wish we can:

• Release a crate only when there are actual changes.
• Verify a crate only when it is being released.
• Minimize the verification workload as much as possible.
• Every crate should have it's own changelog.

Therefore, I believe we can implement our release process as follows:

• Initiate a discussion about the release, with the reqsign version included in the title.
• Run a script to update crate versions based on changes to this crate. The script will also generate a list of crates to be released, along with their corresponding changelogs.
• Run another script to build the ASF release and GitHub release when a new tag is pushed.
  • We may need to investigate how to upload the release tarball directly to SVN.
• Begin a vote on the release (which could potentially be automated).
• After the vote passes, the release manager pushes the official tags to GitHub. The CI pipeline should then proceed to publish the releases.