ci: run the unit tests, and build images only for pull requests and releases

Every push to main published :main and :sha-* images, which nothing pulls.
The libreshop images had grown to 5.8 GB in the registry, on a Gitea host that
is nearly out of space.

- test: npm test for every pull request, every push to main and every release
  tag. It runs in the image's base (Dockerfile FROM, node:22.14.0-alpine), so
  on the runtime's Node, without network and without dependencies. The source
  is piped into the container, because the job container's paths do not exist
  on the Docker host.
- build: after the tests, for a pull request (build only) and for a v* tag
  (build and, with PUBLISH_ENABLED, publish :vX.Y.Z and :latest).

Refs libretech/mp#71

.gitea/workflows/build.yml

@@ -16,14 +16,13 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
-      # The Node version of the image (Dockerfile FROM), so the tests run on the runtime's Node.
+      # The tests need no dependencies. They run in the image's base (Dockerfile FROM), so on the runtime's Node,
-      - uses: actions/setup-node@v4
+      # without network. The source is piped in because the job container's paths do not exist on the Docker host.
-        with:
+      - name: npm test, on the Node of the image
-          node-version: "22.14.0"
+        run: |
-
+          base=$(sed -n 's/^FROM \([^ ]*\).*/\1/p' Dockerfile | head -1)
-      - run: npm test
+          tar -c --exclude=.git . | docker run -i --rm --network none -e npm_config_update_notifier=false "$base" \
-        env:
+            sh -c 'mkdir /w && cd /w && tar -x && npm test'
-          npm_config_update_notifier: "false"
 
   # The image is built to check a pull request, and built and published only for a release tag.
   # Nothing pulls per-commit images, so main no longer publishes :main and :sha-* images.