Always generate a fresh ci-ready label event

Preserve the release-flow invariant that the CI poller always adds ci-ready after CI passes. When an issue enters or re-enters waiting-for-ci, remove any existing ci-ready label before adding ci-pending, even if ci-ready was previously set. Do not optimize away this removal/addition cycle: the fresh labeled event is required to trigger the publish job reliably, especially during retries.