fix(ci): don't deploy to npm on master merge (#3502)

Please provide a paragraph or two giving a summary of the change,
including relevant motivation and context.

# Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if
the PR is ready to merge.
- [ ] If the pull request requires a cryptography review (e.g.
cryptographic algorithm implementations) I have added the 'crypto' tag.
- [ ] I have reviewed my diff in github, line by line and removed
unexpected formatting changes, testing logs, or commented-out code.
- [ ] Every change is related to the PR description.
- [ ] I have
[linked](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue)
this pull request to relevant issues (if any exist).

.circleci/config.yml

@@ -991,7 +991,7 @@ jobs:
             deploy_dockerhub noir x86_64,arm64
             deploy_dockerhub aztec-sandbox x86_64,arm64
             deploy_dockerhub cli x86_64,arm64
-            deploy_dockerhub faucet x86_64,arm64
+            deploy_dockerhub aztec-faucet x86_64,arm64
             deploy_dockerhub mainnet-fork x86_64,arm64
             deploy_dockerhub l1-contracts x86_64,arm64
 

yarn-project/deploy_npm.sh

@@ -2,6 +2,12 @@
 [ -n "${BUILD_SYSTEM_DEBUG:-}" ] && set -x # conditionally trace
 set -eu
 
+# Check we're on a release flow.
+if [ -z "$COMMIT_TAG" ] && [ ! "$DRY_DEPLOY" -eq 1 ]; then
+  echo "Not on a release flow, skipping deploy."
+  exit 0
+fi
+
 extract_repo yarn-project /usr/src project
 cd project/src/yarn-project