ci(supabase_flutter): make WASM tests non-blocking (#1306)

WASM tests have known infrastructure flakiness with 12+ minute loading
timeouts in CI. This causes the entire job to fail due to timeout issues
unrelated to code changes.

Setting continue-on-error: true allows CI to continue while still running
the tests for visibility. The WASM build step is still executed and any
real test failures will be visible in the logs.

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

Author: grdsdev

.github/workflows/supabase_flutter.yml

@@ -88,6 +88,9 @@ jobs:
           cd example && flutter build web
 
       - name: Build and test web (WASM)
+        # WASM tests have known infrastructure flakiness (12min+ loading timeouts)
+        # Allow CI to continue while still running tests for visibility
+        continue-on-error: true
         if: ${{ matrix.os == 'ubuntu-latest' && matrix.flutter-version == '3.x'}}
         run: |
           flutter test --platform chrome --wasm