chore: prepare thread mvp

[bniladridas]

Why
This repo needed the active image flow, setup path, release metadata, and automation names to match the current Thread direction.

Result

• Added a working local API flow for upload, tiling, CPU upscale fallback, stitching, jobs, and output downloads.
• Renamed active project metadata from hybrid-compute to thread.
• Lowered the version to 0.1.0 and aligned Python support to 3.10+.
• Made setup CPU-first, with CUDA, Metal, and native OpenCV optional.
• Quieted README, changelog, security, docs, and workflow names.
• Added API tests and script checks.

Checks

• pre-commit during commit
• .venv/bin/ruff check .
• .venv/bin/ruff format --check .
• .venv/bin/python -m pytest
• ./test_changes.sh
• bash scripts/validate_release_config.sh
• cmake configure and build with CUDA/OpenCV/Metal off
• ctest --test-dir build --output-on-failure

Notes
The README image uses the future thread raw URL. If the repo is not renamed before merge, switch that URL back to hybrid-compute for this PR.

[gpucomm-hq]

👍