Fix import ambiguity regression by reordering AddImport/RemoveImport

[amishra-u]

What's changed?

PR #5439 introduced logic to detect and handle import ambiguity when adding imports. However, this caused some tests to fail due to the order in which imports were being added and removed in some recipes. When new imports were added before the old ones were removed, this led to false positives for ambiguity, resulting in the use of fully qualified names.

This PR addresses the issue by reordering the maybeAddImport and maybeRemoveImport call. Now maybeRemoveImport precedes the maybeAddImport, to avoid premature ambiguity detection.
Additionally, some unit tests contained genuinely ambiguous imports that went undetected earlier. Fixed those test to align with the improved import resolution logic.

Checklist

• I've added unit tests to cover both positive and negative cases
• I've read and applied the recipe conventions and best practices
• I've used the IntelliJ IDEA auto-formatter on affected files

[github-actions]

Some suggestions could not be made:

• src/main/resources/META-INF/rewrite/examples.yml
  • lines 1535-1535
  • lines 1817-1817
  • lines 1825-1825
  • lines 2251-2251
  • lines 2265-2265
  • lines 2443-2503
  • lines 2576-2575

[amishra-u]

CI will pass when this change lands.

• Enhance AddImport to shorten fully qualified names rewrite#5452

[github-actions]

Some suggestions could not be made:

• src/main/resources/META-INF/rewrite/examples.yml
  • lines 1535-1535
  • lines 1817-1817
  • lines 1825-1825
  • lines 2251-2251
  • lines 2265-2265
  • lines 2443-2503
  • lines 2576-2575