_ci_: Forgot a .sh on the end of a the new publish script

[ianconsolata]

Related Issues

This was discovered to be broken during the v1.17.0-rc4 release:
https://github.com/filecoin-project/lotus/releases/tag/v1.17.0-rc4

Failed build:
https://app.circleci.com/pipelines/github/filecoin-project/lotus/22354/workflows/be8a601c-06eb-4a03-a60e-083d50ff99ee

The release artifacts will be manually published for the RC4 release, but we should cherry pick this commit into the 1.17.0 branch to fix the final release. Good news is that except for the typo, it all works as planned (the AppImage release did publish, even though the other ones failed, which was one of the planned changes).

I'm going to evaluate the snapcraft build failure separately, and publish a separate PR fixing it.

Checklist

Before you mark the PR ready for review, please make sure that:

• All commits have a clear commit message.
• The PR title is in the form of of <PR type>: <area>: <change being made>
  • example: fix: mempool: Introduce a cache for valid signatures
  • PR type: fix, feat, INTERFACE BREAKING CHANGE, CONSENSUS BREAKING, build, chore, ci, docs,perf, refactor, revert, style, test
  • area: api, chain, state, vm, data transfer, market, mempool, message, block production, multisig, networking, paychan, proving, sealing, wallet, deps
• This PR has tests for new functionality or change in behaviour
• If new user-facing features are introduced, clear usage guidelines and / or documentation updates should be included in https://lotus.filecoin.io or Discussion Tutorials.
• CI is green

[arajasek]

Ah, that's neat!

The release artifacts will be manually published for the RC4 release, but we should cherry pick this commit into the 1.17.0 branch to fix the final release.

@ianconsolata FYI, you can slap a release/backport label on such PRs -- that's our cue to backport onto the living release branches.