CI add one-time v0.0.2 publication recovery

[BabaSanfour]

Summary

Add a one-time manual recovery workflow for publishing the already-tagged v0.0.2 release.

The workflow:

• is hard-coded to v0.0.2;
• checks out the existing tag without moving it;
• verifies the exact expected release commit;
• rebuilds and validates the wheel and sdist;
• validates the installed wheel and optional integrations;
• publishes those exact validated artifacts using PyPI Trusted Publishing.

Why

The original v0.0.2 release workflow successfully built and validated the release, but its PyPI job could not download release-dists because the tagged workflow predated the missing-artifact upload fix.

The permanent release workflow has already been fixed separately in #128. This workflow exists only to recover v0.0.2 and will be removed after successful publication.

Validation

• spin lint
• git diff --check

No tag, package source, version, changelog, or normal release-workflow changes.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.32%. Comparing base (31be0c2) to head (7370413).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #129   +/-   ##
=======================================
  Coverage   85.32%   85.32%           
=======================================
  Files          77       77           
  Lines       10620    10620           
  Branches     1864     1864           
=======================================
  Hits         9061     9061           
  Misses        935      935           
  Partials      624      624           

Flag	Coverage Δ
unittests	85.32% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.