GitHub Actions: push event job prioritized over release after GH release

Upon adding a [new release](https://github.com/zio/interop-cats/releases/tag/v23.1.0.11) via GitHub Releases UI with the option enabled to create a new tag, two jobs were spawned: a job with 'release' event and a job with 'push' on the same commit. Subsequently the [release job](https://github.com/zio/interop-cats/actions/runs/19762833575) was canceled in favor of the [push job](https://github.com/zio/interop-cats/actions/runs/19762833580) – this prevented release-only steps 'Release Docs' & 'Notify Docs Release' from being started. ``` Canceling since a higher priority waiting request for CI-refs/tags/v23.1.0.11 exists ``` If release job is restarted, it would fail its 'Release' step because the artifacts were already published to Sonatype by the push job.