debug: Add comprehensive debugging to analysis workflow

Add extensive debugging output to understand the state after melos bootstrap:
- Check if pubspec_overrides.yaml files are created
- List directory contents and structure
- Show pubspec.yaml contents for each package
- Check .pub-cache and .dart_tool directories
- Run flutter pub deps to see dependency resolution
- Display current working directories

This will help diagnose why dart-package-analyzer is failing
and whether melos is properly creating the override files.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: ened

.github/workflows/analysis.yml

@@ -14,6 +14,31 @@ jobs:
           channel: "stable"
           cache: true
       - uses: bluefireteam/melos-action@v3
+      - name: Debug package state
+        run: |
+          echo "=== Current working directory ==="
+          pwd
+          echo "=== Root directory contents ==="
+          ls -la
+          echo "=== Checking ${{ matrix.package }} directory ==="
+          cd ${{ matrix.package }}
+          pwd
+          ls -la
+          echo "=== pubspec.yaml contents ==="
+          cat pubspec.yaml
+          echo "=== pubspec_overrides.yaml exists? ==="
+          if [ -f pubspec_overrides.yaml ]; then
+            echo "YES - pubspec_overrides.yaml exists"
+            cat pubspec_overrides.yaml
+          else
+            echo "NO - pubspec_overrides.yaml does not exist"
+          fi
+          echo "=== .pub-cache directory ==="
+          ls -la .pub-cache/ || echo "No .pub-cache directory"
+          echo "=== .dart_tool directory ==="
+          ls -la .dart_tool/ || echo "No .dart_tool directory"
+          echo "=== Flutter pub deps ==="
+          flutter pub deps || echo "Flutter pub deps failed"
       - uses: axel-op/dart-package-analyzer@v3
         with:
           githubToken: ${{ secrets.GITHUB_TOKEN }}