Prepare the project for 0.1.0 release

[jiayuasu]

This pull request significantly improves the release process documentation and automation for Apache Sedona SpatialBench, with a focus on making verification, signing, and publishing more robust and user-friendly. The changes include a major rewrite of the release instructions, enhanced scripts for license checking, and simplification of asset signing and upload procedures. Bash scripts for signing and uploading release assets have been removed in favor of clear manual instructions. The README now provides step-by-step guidance for all release stages, including crates.io publishing.

Release process improvements:

• The dev/release/README.md has been extensively rewritten to clarify and expand instructions for verifying, signing, and publishing releases, including new sections for local testing, tarball creation, signature generation, checksum verification, SVN upload, and crates.io publishing. [1] [2]
• Manual signing and upload instructions replace previous bash automation scripts, with the removal of dev/release/sign-assets.sh, dev/release/upload-candidate.sh, and dev/release/upload-release.sh. [1] [2] [3]

Verification and license checking enhancements:

• The release verification script now requires java and python, and adds an explicit Apache RAT license check as part of the verification flow. [1] [2] [3] [4]
• The RAT exclusion list in dev/release/rat_exclude_files.txt has been updated to exclude all files in spatialbench/data/** and several additional project and documentation files.
• The run-rat.sh script now ensures RAT is run from the target directory, uses Python 3, and outputs relative paths for easier review. [1] [2]

Metadata and versioning updates:

• The workspace package version in Cargo.toml has been reset to 0.1.0 and a project description has been added.

Robustness and error handling:

• Improved error handling in the release verification script for missing dependencies and failed downloads, with clear instructions for local testing.

These updates make the release workflow more transparent, reproducible, and maintainable for future contributors.