Don't remove mockStatic() calls in resources of try-with-resources

[knutwannheden]

This commit does not yet close the issue, as there are other cases, where this can potentially go wrong.

It also appears strange that the recipe matches on Mockito's mockStatic() rather than on PowerMock's mockStatic(). Therefore, the recipe is for now excluded from Mockito1to3Migration, as this is part of JUnit4to5Migration which is widely used.

Issue: #360

[knutwannheden]

@timtebeek We should take a fresh look at this PowerMock recipe. The thing with the mockStatic() matcher looks really odd to me. I also don't understand why the recipe uses a precondition like

rewrite-testing-frameworks/src/main/java/org/openrewrite/java/testing/mockito/PowerMockitoMockStaticToMockito.java

Lines 45 to 48 in de6b6a8

	Preconditions.or(
	new UsesType<>("org.powermock..*", false),
	new UsesType<>("org.mockito..*", false)
	),

rather than only checking for PowerMock.

[timtebeek]

@timtebeek We should take a fresh look at this PowerMock recipe. The thing with the mockStatic() matcher looks really odd to me. I also don't understand why the recipe uses a precondition like

rather than only checking for PowerMock.

Agree that's odd; would only migrate when there's a confusing mix of libraries in use in a source file already? We can loosen that restriction as part of this PR, especially now that it's not part of the default set of recipes run anymore in larger composed migrations.