v0.0.1 chore: prepare crates.io release

[adamcavendish]

Summary

Prepare the initial 0.0.1 crates.io release.

• Set Cargo/CLI version to 0.0.1 and derive OpenAPI version metadata from Cargo, with regression coverage.
• Add crates.io package metadata and the initial CHANGELOG.md.
• Add just publish and just publish-dry-run, explicitly targeting crates.io with package verification enabled.
• Add an independent crate dry-run CI job covered by the aggregate delivery gate.

Release ownership

The maintainer will create and push v0.0.1 on the final release commit.
This PR does not create tags or upload to crates.io, GitHub Releases or a container registry.
After merge and successful CI, run just publish from a clean checkout of that exact commit with crates.io credentials.

Verification

• Formatting, Clippy and default/Turso tests passed.
• Actual PostgreSQL contracts, both backend SDK/restart examples and recursive SDK compilation passed.
• Release binary reports sqlrest 0.0.1; container lifecycle passed.
• just publish-dry-run passed from a clean committed tree: packaged 117 files and rebuilt the extracted crate; upload was explicitly aborted by dry-run.
• Actionlint and diff whitespace checks passed.
• just --dry-run publish confirms the actual command without executing it.
• Direct pre-landing and independent documentation/coverage reviews found no actionable issues.

Dry-run does not verify crates.io ownership/token permissions or reserve a crate name.

Documentation

Add the initial changelog and README link, describe manual crates.io publication and tagging, document the new CI gate, and correct the SDK prerequisite text to refer to Justfile.