Avoid panic when analyze graph hits broken pipe

[charliermarsh]

Summary

I think we should also make the change that @BurntSushi recommended in the linked issue, but this gets rid of the panic.

See: #13483

See: #13442

Test Plan

warning: `ruff analyze graph` is experimental and may change without warning
{
  "/Users/crmarsh/workspace/django/django/__init__.py": [
    "/Users/crmarsh/workspace/django/django/apps/__init__.py",
    "/Users/crmarsh/workspace/django/django/conf/__init__.py",
    "/Users/crmarsh/workspace/django/django/urls/__init__.py",
    "/Users/crmarsh/workspace/django/django/utils/log.py",
    "/Users/crmarsh/workspace/django/django/utils/version.py"
  ],
  "/Users/crmarsh/workspace/django/django/__main__.py": [
    "/Users/crmarsh/workspace/django/django/core/management/__init__.py"
ruff failed
  Cause: Broken pipe (os error 32)

[BurntSushi]

I think this is an improvement over panicking, but the "ruff failed" message and the failure exit code is probably non-ideal and probably not what the user expects.

[charliermarsh]

That’s covered in #13485 since it affects more than this subcommand.

[github-actions]

ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

✅ ecosystem check detected no linter changes.