Fix pylint disable-next comments at the start of imports

[Neallin-917]

Summary

• keep a leading pylint: disable-next directive with the import it governs
• add a regression test for sorting two such from-imports

Closes #2054

Testing

• uv run pytest tests/unit/test_regressions.py
• uv run tox -e py3.13

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.36%. Comparing base (d5f40fa) to head (47460eb).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2628   +/-   ##
=======================================
  Coverage   99.36%   99.36%           
=======================================
  Files          41       41           
  Lines        3165     3166    +1     
  Branches      682      682           
=======================================
+ Hits         3145     3146    +1     
  Misses         12       12           
  Partials        8        8           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[DanielNoord]

Please rebase this as well to get the new CI setup!

[DanielNoord]

Please change the content of the comments to show that they are properly attached to the imports by differentiating them

[DanielNoord]

@Neallin-917 Please see this comment :)

[Neallin-917]

Rebased onto current main in 47460eb to pick up the new CI setup. The targeted regression suite, Ruff checks, and the updated PR checks are green. Thanks!

[Neallin-917]

Addressed in 3bf67d5. The two pylint: disable-next comments now use distinct valid Pylint codes, so the expected sorted output proves each comment remains attached to its respective import. uv run pytest tests/unit/test_regressions.py passes (94 tests), along with Ruff and formatting checks.