Ignore cancelled port status producers

[shai-almog]

What changed

• require a successful upstream workflow conclusion before publishing Port Status artifacts
• ignore cancelled or failed producer runs instead of launching a misleading publisher failure

Root cause

Run 29551726398 was triggered by cancelled Mac producer run 29551613034. The publisher only checked the upstream event and branch, so it attempted to download artifacts from a run that never produced any and failed with No normalized port reports were found.

Validation

• git diff --check
• parsed .github/workflows/port-status-publish.yml with Ruby YAML

[github-actions]

✅ Continuous Quality Report

Test & Coverage

• ✅ Tests: 4184 total, 0 failed, 1 skipped
• 📊 Line coverage: 57.43% [HTML preview] [Download]
  • Lowest covered classes
    • com.codename1.gaming.level.GameSceneView – 0.00%
    • com.codename1.crash.CrashProtection – 0.00%
    • com.codename1.payment.CommerceManager – 0.00%
    • com.codename1.crash.PiiScrubber – 0.00%
    • com.codename1.crash.CrashReportPayload – 0.00%
    • com.codename1.vr.VRView – 0.00%
    • com.codename1.appreview.RatingDialog – 0.00%
    • com.codename1.security.Secrets – 0.00%
    • com.codename1.vr.VRView$EyeLoop – 0.00%
    • com.codename1.gaming.level.TileLayer – 0.00%

Static Analysis

• SpotBugs [Report archive]
  • ✅ ByteCodeTranslator: 0 findings (no issues)
  • ✅ android: 0 findings (no issues)
  • ✅ codenameone-maven-plugin: 0 findings (no issues)
  • ✅ core-unittests: 0 findings (no issues)
  • ✅ ios: 0 findings (no issues)
• ✅ PMD: 0 findings (no issues) [Report archive]
• ✅ Checkstyle: 0 findings (no issues) [Report archive]

Generated automatically by the PR CI workflow.