Refine warning about incompatible isort settings

[MichaReiser]

Summary

This PR refines the warning shown when running ruff format about incompatible isort settings:

• Only warn if I001 (unsorted imports) is enabled.

• lines-after-imports: Warn about values other than -1, 1, and 2` because the formatter enforces at least one empty and at most two empty lines after imports.

• lines-between-types: Warn about values > 1 because the formatter preserves at most one empty line in nested import blocks.

• split_on_trailing_comma: Only warn when skip-magic-trailing-comma is true to ensure the formatter preserves the trailing commas.

• Remove force-single-line: I think removing the warnings is safe. The setting seems to mainly be about removing parentheses around alieses:

  from .utils2 import (
    test_directory as test_directory,
  )
  from .utils2 import (
      test_id as test_id,
  )
  
   # isorted
  from .utils import (
    test_directory as teeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee,
  )
  from .utils import test_id as t2
  from .utils2 import test_directory as test_directory
  from .utils2 import test_id as test_id  

  which the formatter leaves unchanged

• Only warn about force_wrap_aliases when skip-magic-trailing-comma is true. Isort inserts trailing commas that the formatter respects, except when skip-magic-trailing-comma isn't set to true.

Test Plan

Added test plans. Played around with different examples in the playground to identify the isort behavior.

[MichaReiser]

Current dependencies on/for this PR:

• main
  • PR Refine warning about incompatible isort settings #8192 👈
    • PR Refine the warnings about incompatible linter options #8196
      • PR Don't warn about magic trailing comma when isort.force-single-line is true #8244

This comment was auto-generated by Graphite.

[github-actions]

PR Check Results

Ecosystem

✅ ecosystem check detected no changes.

[MichaReiser]

@charliermarsh you have a better understanding of isort than I. I would appreciate if you could review the compatibility in detail to make sure we get it right this time.

[charliermarsh]

These look correct to me. I also scanned through the full list of options and confirmed the omitted settings seem compatible too.