test: ignore errors related to workflow screen recording

the screen recordings are nice to have for forensics, but not an
indicator of whether the test run itself is succeeding

at same time screen recording setup apperas to fail 3-4% of the time
and is now one of the most significant sources of flakiness, so continue
if that's the only problem

Author: mikehardy

.github/workflows/tests_e2e_ios.yml

@@ -103,11 +103,13 @@ jobs:
     steps:
       - name: Setup Environment for Screen Recording
         uses: guidepup/[email protected]
+        continue-on-error: true
         with:
           record: true
 
       - name: Upload Screen Recording Environment Setup
         uses: actions/upload-artifact@v4
+        continue-on-error: true
         if: always()
         with:
           name: screenrecording-setup-${{ matrix.buildmode }}-${{ matrix.iteration }}.mov

.github/workflows/tests_e2e_other.yml

@@ -98,11 +98,13 @@ jobs:
     steps:
       - name: Setup Environment for Screen Recording
         uses: guidepup/[email protected]
+        continue-on-error: true
         with:
           record: true
 
       - name: Upload Screen Recording Environment Setup
         uses: actions/upload-artifact@v4
+        continue-on-error: true
         if: always()
         with:
           name: screenrecording-setup-${{ matrix.iteration }}.mov
@@ -235,6 +237,7 @@ jobs:
           echo "...javascript bundle ready"
 
       - name: Start Screen Recording and System Logging
+        continue-on-error: true
         run: |
           nohup sh -c "sleep 314159265 | screencapture -v -C -k -T0 -g screenrecording.mov > screenrecording.log 2>&1 &"
           nohup sh -c "log stream --backtrace --color none --style syslog > syslog.log 2>&1 &"