CI: Split 'yarn build' and 'yarn build:apm' into separate steps

It's important that the CI job does not continue if 'yarn build'
fails.

The previous syntax was running 'yarn run build:apm' unconditionally
after 'yarn build', regardless of exit status. So, a failure in
'yarn build' would be followed by a 'yarn run build:apm', which
could succeed, and the overall CI job could proceed with broken
native C/C++ addon modules (effectively a broken app!) as if nothing
had failed at any point. Not good!

Prevent broken app builds from passing in CI by ensuring these steps
are each evaluated separately.

Author: DeeDeeG

.github/workflows/build.yml

@@ -155,15 +155,21 @@ jobs:
         command: yarn install --ignore-engines
         on_retry_command: rm -R node_modules
 
-    - name: Build Pulsar
+    - name: Rebuild Pulsar Dependencies for Electron
       uses: nick-fields/retry@7152eba30c6575329ac0576536151aca5a72780e
       with:
         timeout_minutes: 30
         max_attempts: 3
         retry_on: error
-        command: |
-          yarn build
-          yarn run build:apm
+        command: yarn build
+
+    - name: Build ppm
+      uses: nick-fields/retry@7152eba30c6575329ac0576536151aca5a72780e
+      with:
+        timeout_minutes: 30
+        max_attempts: 3
+        retry_on: error
+        command: yarn build:apm
 
     - name: Cache Pulsar dependencies - Linux
       if: ${{ runner.os == 'Linux' }}