ci: Calls build_and_publish directly from release-please. (#282)

# What ❔

Calls build_and_publish directly from release-please.

<!-- What are the changes this PR brings about? -->
<!-- Example: This PR adds a PR template to the repo. -->
<!-- (For bigger PRs adding more context is appreciated) -->

## Why ❔

This allows to use GITHUB_TOKEN.

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

.github/workflows/build_and_publish.yml

@@ -1,6 +1,7 @@
 name: Build and publish era-withdrawal-finalizer image
 
 on:
+  workflow_call:
   push:
     tags:
       - v*

.github/workflows/release-please.yml

@@ -20,11 +20,15 @@ jobs:
           command: manifest
           config-file: .github/release-please/config.json
           manifest-file: .github/release-please/manifest.json
-          token: ${{ secrets.ZKSYNC_ADMIN_BOT_ORG_REPO_WRITE }}
-          
+          token: ${{ secrets.GITHUB_TOKEN }}
+
       - name: Send Release Info
         if: ${{ steps.release.outputs.releases_created }}
         uses: matter-labs/format-release-please-for-slack-action@69e6fe9e4ec531b7b5fb0d826f73c190db83cf42 # v2.1.0
         with:
           release-please-output: ${{ toJSON(steps.release.outputs) }}
           slack-webhook-url: ${{ secrets.SLACK_WEBHOOK_RELEASES }}
+
+      - name: Build and publish
+        if: ${{ steps.release.outputs.releases_created }}
+        uses: ./.github/workflows/build_and_publish.yml