release: running npm audit signatures is not necessary during publish

it is interesting, but not required, and it fails if for instance you
have a release that isn't published on npm. Which happens to be exactly
the situation right now for this package, so it breaks publishing

.github/workflows/publish.yml

@@ -32,8 +32,6 @@ jobs:
       # there will be errors related to pod-install but we can ignore them
       - name: Install dependencies using NPM
         run: npm i
-      - name: Verify the integrity of provenance attestations and registry signatures for installed dependencies
-        run: npm audit signatures
       - name: Release
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}