Release job's MCP registry publish retry doesn't cover connection timeouts or expired JWT

[Mearman]

Two more failure modes of the Release job's MCP-registry publish step turned up today that `isRetryablePublishFailure` (src/core/mcp-registry-retry.ts) doesn't recognise, so the release fails outright instead of retrying:

• Run https://github.com/ExaDev/agent-comms/actions/runs/35249771867 (v3.9.0, triggered by merging feat: default cc-peer front (slot identity, yield, dedup) #171): `Error: publish failed: error sending request: Post "https://registry.modelcontextprotocol.io/v0/publish": dial tcp 34.61.200.254:443: i/o timeout` -- a raw connection-level failure with no HTTP status at all, so neither the propagation-lag text check nor the 5xx pattern matches it.
• Run https://github.com/ExaDev/agent-comms/actions/runs/35239013253 (same v3.9.0, triggered by an unrelated commit merged about 100 minutes earlier the same day): `Error: publish failed: server returned status 401: {"title":"Unauthorized","status":401,"detail":"Invalid or expired Registry JWT token",...}`. `mcp-publisher login github-oidc` runs once before the retry loop starts; if the retry loop runs long enough (up to the 15-minute budget) the JWT it logged in with can expire before a later retry attempt, and `isRetryablePublishFailure` doesn't classify a 401 as retryable at all.

Net effect: both runs left a git tag (v3.9.0) created and pushed, but no npm package and no GitHub release for that version -- confirmed directly against the npm registry (`agent-comms@3.9.0` 404s) and the tag list (`v3.9.0` exists, `npm view agent-comms version` still reports 3.8.0).

Two independent fixes, both following this file's own established pattern of adding a newly-observed retryable failure class with an incident comment:

1. Add a connection-level-error check to `isRetryablePublishFailure` (matching `dial tcp`, `i/o timeout`, `connection refused`, or similar Go net-error text mcp-publisher's own HTTP client would produce) alongside the existing propagation-lag and 5xx checks.
2. For the JWT-expiry case, either re-run `mcp-publisher login github-oidc` before each retry attempt (not just once up front), or treat a 401 with "expired" in the body as retryable only after re-logging in first -- retrying the same expired token would just 401 again.

Filed while merging #157; unrelated to that PR's own diff, which is why it's a separate issue rather than a fix bundled into it.

[github-actions]

🎉 This issue has been resolved in version 3.11.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• v3.11.0
• GitHub release

Your semantic-release bot 📦🚀