Always place non-relative imports after relative imports

[charliermarsh]

Summary

When relative-imports-order = "closest-to-furthest" is set, we should still put non-relative imports after relative imports. It's rare for them to be in the same section, but possible if you use known-local-folder.

Closes #10655.

Test Plan

New tests.

Also sorted this file:

from ..models import ABC
from .models import Question
from .utils import create_question
from django_polls.apps.polls.models import Choice

With both:

• isort view.py
• ruff check view.py --select I --fix

And the following pyproject.toml:

[tool.ruff.lint.isort]
order-by-type = false
relative-imports-order = "closest-to-furthest"
known-local-folder = ["django_polls"]

[tool.isort]
profile = "black"
reverse_relative = true
known_local_folder = ["django_polls"]

I verified that Ruff and isort gave the same result, and that they still gave the same result when removing the relevant setting:

[tool.ruff.lint.isort]
order-by-type = false
known-local-folder = ["django_polls"]

[tool.isort]
profile = "black"
known_local_folder = ["django_polls"]

[github-actions]

ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

✅ ecosystem check detected no linter changes.