add document for how to release and how to verify a release

[luoyuxia]

Purpose

Linked issue: close #213

Add release documentation and supporting scripts for Apache Paimon Rust, covering how to create a release and how to verify a release candidate.

Brief change log

• Add docs/src/release/creating-a-release.md: step-by-step guide for creating a release, including GPG setup, dependency list generation, release branch management, source tarball creation, SVN staging, voting process, and release promotion.
• Add docs/src/release/verifying-a-release-candidate.md: guide for verifying an RC, including signature/checksum verification, build verification, LICENSE/NOTICE checks, and per-component testing (Rust, Python, Go).
• Add scripts/release.sh: automates source tarball creation, GPG signing, and checksum generation.
• Add scripts/bump-version.sh: bumps workspace version in root Cargo.toml (scoped to [workspace.package] only).
• Add scripts/dependencies.py and scripts/constants.py: generates DEPENDENCIES.rust.tsv files for ASF license compliance.
• Add bindings/go/DEPENDENCIES.md and TSV files for Go binding dependency tracking.
• Update NOTICE and bindings/python/NOTICE copyright year to 2024-2026.
• Update docs/mkdocs.yml to include the new release documentation pages.
• Update Cargo.toml workspace version from 0.0.0 to 0.1.0.
• Update .licenserc.yaml to exclude DEPENDENCIES.*.tsv from license header checks.

Tests

Documentation and script changes only. No code logic changes to test.
The whole workflow has been verified by fluss-rust

API and Format

No.

Documentation

Yes. This PR adds the release guide and verification guide to the project website under the "Releases" section.

[JingsongLi]

+1 Thanks @luoyuxia !