Add recipes to migrate boxed primitive constructors deprecated in Java 9

[dsibilio]

What's changed?

Added a set of Refaster recipes to deal with boxed primitive constructors that were deprecated in Java 9.

What's your motivation?

https://rewriteoss.slack.com/archives/C01A843MWG5/p1698430647117759?thread_ts=1698429230.444949&cid=C01A843MWG5

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

Unless I missed something, I think I covered all deprecated constructors except new Float(double) -> Float.valueOf((float) double). Due to how Refaster generates the code, I end up in a situation like the following:

Refaster Template

@RecipeDescriptor(
    name = "Replace deprecated `Float(double)` constructor invocations",
    description = "Replace deprecated `Float(double)` constructor invocations with `Float.valueOf((float) double)`."
)
public static class FloatDoubleConstructor {
    @BeforeTemplate
    public Float doubleConstructor(double value) {
        return new Float(value);
    }

    @AfterTemplate
    public Float valueOf(double value) {
        return Float.valueOf((float) value);
    }
}

Generated Code Error

error: incompatible types: Double cannot be converted to float
                final JavaTemplate valueOf = Semantics.expression(this, "valueOf", (@Primitive Double value) -> Float.valueOf((float)value)).build();

Therefore I was only able to cover new Float(Double) -> new Float(Double.floatValue()) instead.

Is there any way to force a real primitive in this line via Refaster (or use e.g.: a String-format template somehow)?
Do we need to make a separate imperative recipe just to cover the Float(double) edge case?

Anyone you would like to review specifically?

@timtebeek 🙏

Have you considered any alternatives or workarounds?

We could use imperative recipes but the change seems simple enough that the Refaster usage seems to be justified and seems to avoid a lot of repeated boilerplate code.

Any additional context

Checklist

• I've added unit tests to cover both positive and negative cases
• I've added the license header to any new files through ./gradlew licenseFormat
• I've used the IntelliJ IDEA auto-formatter on affected files

[timtebeek]

Appreciate the quick turn around on this & thanks for contributing.

I don't know of a way to force the case for new Float(double) using Refaster; I think we can leave that out for now; it should be uncommon, and perhaps not worth the effort of a separate recipe.

Really like how you cover every case with a single test, and how you took care to match our expected formatting.