getsentry/craft publish recovery: check completed targets before retry to avoid duplicate-publish 403

When a craft publish run fails mid-way (e.g., docker[release] 400 Bad Request), some targets (npm, gcs, registry) may have already succeeded. Recovery steps: (1) verify which targets completed (check npm registry, GCS bucket, release-registry repo); (2) update the publish issue body to check off completed targets; (3) re-add the 'accepted' label to re-trigger the publish workflow — it will skip already-checked targets. Always verify npm publish before retry to avoid duplicate-publish 403. Docker Hub 400 during blob upload is a known transient infrastructure flake — retry resolves it.