chore(ci): publish only when there is a release

[sasjs-dev]

Publishes only when semantic-release actually cut a release, the same guard as sasjs/adapter#902.

The failure this fixes. The publish step ran on if: success() regardless of whether semantic-release released anything:

       - name: Publish to npm with trusted publisher
+        id: publish
         if: success()
-        run: npm publish --access public
+        run: |
+          local_version=$(node -p "require('./package.json').version")
+          published_version=$(npm view @sasjs/lint version 2>/dev/null || echo "")
+
+          if [ "$local_version" = "$published_version" ]; then
+            echo "released=false" >> "$GITHUB_OUTPUT"
+            echo "Nothing to publish - $local_version is already on npm"
+            exit 0
+          fi
+
+          npm publish --access public
+          echo "released=true" >> "$GITHUB_OUTPUT"

The angular convention does not treat chore: or docs: as releasable, so a merge with no releasable commit left package.json at the version already on npm, and npm publish was rejected with "You cannot publish over the previously published versions". That is the red run earlier today on a docs(lint): merge. It is a no-op now instead.

Verified both branches, with a stubbed npm on PATH so the publish path runs without publishing anything:

local == published    exit=0  "Nothing to publish - 4.1.1 is already on npm"
                     GITHUB_OUTPUT: released=false
                     npm publish called: no

local != published   exit=0  GITHUB_OUTPUT: released=true
                     npm publish called: publish --access public

The workflow still parses (prettier exit 0).

Typed chore(ci) with [skip release] deliberately: this is CI-only, no consumer sees a difference, and a patch release would be version churn.

[sasjs-gha]

🎉 This PR is included in version 4.1.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀