fix(root): unblock express jobs in npmjs-release

#8650 introduced an `always()` chain on `release-bitgojs` so it can
run when one of its two context jobs is skipped (get-release-context
in recovery mode, get-recovery-context in normal mode). The Express
jobs (get-express-release-context, publish-express-to-docker-hub)
relied on GHA's implicit `success()` against `release-bitgojs`, which
propagates the skipped context-job status as not-success along the
chain. Express therefore skips on both modes even though release-
bitgojs itself succeeded.

Override with explicit `always() && needs.<>.result == 'success'` on
both Express jobs so the docker publish runs whenever release-bitgojs
actually succeeded, regardless of which context job ran.

Ticket: WCN-357

Author: zahin-mohammad

.github/workflows/npmjs-release.yml

@@ -318,7 +318,7 @@ jobs:
 
   get-express-release-context:
     name: Get Express release context
-    if: inputs.dry-run == false
+    if: ${{ always() && inputs.dry-run == false && needs.release-bitgojs.result == 'success' }}
     needs:
       - release-bitgojs
     runs-on: ${{ vars.BASE_RUNNER_TYPE || 'ubuntu-latest' }}
@@ -411,7 +411,7 @@ jobs:
 
   publish-express-to-docker-hub:
     name: Publish Express To Docker Hub
-    if: needs.get-express-release-context.outputs.docker-exists != 'true'
+    if: ${{ always() && needs.get-express-release-context.result == 'success' && needs.get-express-release-context.outputs.docker-exists != 'true' }}
     needs:
       - get-express-release-context
     runs-on: ${{ vars.BASE_RUNNER_TYPE || 'ubuntu-latest' }}