ci: drop --no-fatal-infos from the analyze steps

Both workflows invoke `flutter analyze --no-fatal-infos` directly rather
than going through `./bin/mise run analyze`, so without this the previous
commit only tightens the local gate and CI stays advisory — which is the
regression #524 is about.

`.github/workflows/` is on the AGENTS.md Do-Not-Modify list, so this is
kept as a separate commit: it can be dropped on its own if the maintainer
would rather have the workflows call the mise task instead.

Refs #524

Author: claude

.github/workflows/ci.yml

@@ -155,7 +155,7 @@ jobs:
           generate-mocks: 'true'
 
       - name: Analyze code
-        run: flutter analyze --no-fatal-infos
+        run: flutter analyze
 
   # Run tests once before building
   test:

.github/workflows/release-web.yml

@@ -40,7 +40,7 @@ jobs:
           generate-mocks: 'true'
 
       - name: Analyze code
-        run: flutter analyze --no-fatal-infos
+        run: flutter analyze
 
       - name: Run tests
         run: flutter test