…nner (#942)

ReplacePowerMockito was ordered after AddMockitoExtensionIfAnnotationsUsed,
so the latter would see @RunWith(PowerMockRunner.class) and skip the class.
Then ReplacePowerMockito would remove it, leaving @mock fields uninitialized.

Move ReplacePowerMockito before AddMockitoExtensionIfAnnotationsUsed so the
runner gap is detected and filled with MockitoJUnitRunner or MockitoExtension.

…943)

* Refactor PowerMockitoMockStaticToMockito for clarity and single responsibility

Extract independent responsibilities from the monolithic 557-line recipe:

- Extract `RemovePowerMockClassExtensions` recipe for removing
  `extends PowerMockConfiguration` and `extends PowerMockTestCase`
- Fold `@RunWith(PowerMockRunner.class)` removal (with and without
  delegate) into `PowerMockRunnerDelegateToRunWith`
- Replace 8 mutable instance fields with a `TestFramework` enum
- Add early returns throughout to reduce nesting and improve readability

* Clean up PowerMockitoMockStaticToMockito visitor

- Consolidate isStaticMockAlreadyClosed/isStaticMockAlreadyOpened into
  single hasMatchingInvocation method parameterized by MethodMatcher
- Restructure visitMethodInvocation with early returns for clarity
- Fix double getTestGroupsAsString() call in maybeAddTearDownMethodBody
- Simplify mockStatic tracking to use direct list access instead of
  Optional stream

* Improve PowerMockRunnerDelegateToRunWith per review feedback

- Use service(AnnotationService.class) instead of manual stream check
- Extract findDelegateRunnerArg method to avoid finalDelegateRunnerArg
- Move shared maybeRemoveImport(POWER_MOCK_RUNNER) above if/else so
  each branch can return immediately

* Move import removal before withLeadingAnnotations for immediate returns

* Update src/main/java/org/openrewrite/java/testing/mockito/PowerMockRunnerDelegateToRunWith.java

* Add PowerMockWhiteboxToJavaReflection recipe

Replace `org.powermock.reflect.Whitebox` calls with plain Java
reflection as part of the ReplacePowerMockito recipe chain.

Handles setInternalState, getInternalState, and invokeMethod by
expanding each call into getDeclaredField/getDeclaredMethod +
setAccessible + get/set/invoke. Uses VariableNameUtils to avoid
name collisions when multiple Whitebox calls target the same field.

* Regenerate recipes.csv to include PowerMockWhiteboxToJavaReflection

* Add powermock-reflect-1.6.5 classpath JAR for type resolution

* Regenerate classpath type table to include powermock-reflect

The classpath.tsv.gz type table is what CI uses for type resolution
in tests. The previously committed JAR is unnecessary when the type
table includes the artifact.

* Address review feedback on PowerMockWhiteboxToJavaReflection

- Inline the named WhiteboxVisitor into an anonymous class
- Use immediate return for maybeAutoFormat
- Remove unnecessary powermock-reflect-1 classpath from integration test

* Fix template type attribution by using #{any(java.lang.Object)}

Untyped #{any()} placeholders caused the template parser to infer the
argument's actual type (e.g. MyService), which is not on the template
parser's classpath. This broke type resolution for the entire method
chain (.getClass(), .getDeclaredField(), .setAccessible(), etc.).

Using #{any(java.lang.Object)} ensures the substitution always resolves
against a JDK type, fixing type attribution. Also inlines the JAVA_PARSER
field and removes the now-unnecessary methodInvocations(false) from the
unit test.

---------

Co-authored-by: Tim te Beek <[email protected]>

Resolve the target method's declared parameter types from the AST
instead of using arg.getClass() which returns the runtime concrete
class and fails when the method parameter is an interface/parent type.

Three-tier resolution strategy:
1. Resolve the target method declaration and use its parameter types
2. Fall back to the argument's compile-time type
3. Fall back to arg.getClass() when no type info is available