Consider re-enabling UnusedUseStatement and UnsortedUseStatements PHPCS rules

[alistair3149]

Re-enable two PHPCS rules that are currently excluded in phpcs.xml:

• MediaWiki.Classes.UnusedUseStatement.UnusedUse
• MediaWiki.Classes.UnsortedUseStatements.UnsortedUse

UnusedUseStatement: Nothing in the toolchain currently catches unused use imports — PHPStan doesn't check this at any level, and Psalm's findUnusedCode doesn't cover it either. Re-enabling this rule closes that gap.

UnsortedUseStatements: Enforcing a consistent import order improves scannability and reduces merge conflicts in import blocks. The one-time churn of sorting existing files is minimal.

Result of exploratory discussion with @alistair3149.
Context: NeoWiki PHPCS, PHPStan, and Psalm configurations.
_{Written by Claude Code, Opus 4.6}

[JeroenDeDauw]

Are those things actually slowing us down? Especially with the way we write code now?

I think that if everyone uses a decent editor that has these statements collapsed by default and adds/removes them automatically, these rules gain you little. That's why I started dropping them 5-6 years ago. Now with AI tools the benefit seems even less.

I suspect the friction caused by these rules is notably higher than the grain of their benefits.

[alistair3149]

Are those things actually slowing us down? Especially with the way we write code now?

I see it in a different light. Because of the way we write code now, we don't have the friction and annoyance anymore caused by these rules. Having more consistency helps AI making the right decisions.