Skip wrapper-primitive in UseAssertSame; rewrite via AssertTrueComparisonToAssertEquals

[motlin]

What's changed?

For an input like:

Map<String, Double> map = new HashMap<>();
double primitive = 0.5;
assertTrue(map.get("k") == primitive);

UseAssertSame was rewriting it to:

assertSame(map.get("k"), primitive);

It should rewrite to:

assertEquals(map.get("k"), primitive);

To get there:

• UseAssertSame now skips when either operand is a Java primitive (with Null and String carved out, since OpenRewrite encodes both as JavaType.Primitive enum values but their == is reference equality).
• AssertTrueComparisonToAssertEquals now also accepts mixed primitive-wrapper operands. Wrapper-wrapper is still rejected.

What's your motivation?

• PR Skip primitive comparisons in UseAssertSame #992 added a primitive-primitive skip to UseAssertSame, which catches assertTrue(123L == 123).

The rewritten assertSame fails at runtime because Java's == unboxes, but assertSame autoboxes the primitive into a fresh wrapper and compares by reference:

expected: java.lang.Double@4130a648<0.5>
but was:  java.lang.Double@61ff6a49<0.5>

Anything in particular you'd like reviewers to focus on?

Wrapper-wrapper is left to UseAssertSame rather than swept into AssertTrueComparisonToAssertEquals, since rewriting Double == Double to value equality would silently change semantics on intentional reference checks.

Anyone you would like to review specifically?

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

[timtebeek]

Thanks a lot! More comprehensive than the previous attempt indeed.