fix(release): accept github pr suffix on release commits

[JSONbored]

Summary

• fix the manual release publish workflow so it can find release commits merged with GitHub's default PR-number suffix

What changed

• updated the publish path in .github/workflows/release.yml
• release commit detection now accepts either:
  • chore(release): vX.Y.Z-aio.N
  • chore(release): vX.Y.Z-aio.N (#123)
• added a clearer error message when no matching release commit is found

Why

• the existing workflow expected an exact commit subject match
• GitHub commonly merges PRs with a final subject like chore(release): v0.6.9-aio.1 (#24)
• that caused publish to fail even though the release PR and changelog were already merged correctly

Validation

• verified origin/main contains chore(release): v0.6.9-aio.1 (#24)
• verified the updated matching logic resolves that commit correctly

Notes

• this is a release-workflow fix only
• after merging this PR, re-run Release / Sure-AIO with action=publish on main