Remove try catch fail blocks should be selectively applied

[AlekSimpson]

What's changed?

The new try catch recipe was not handling cases where binary expressions were being passed into Assertions.fail correctly. This PR fixes that.

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 auto-formatter on affected files
• I've updated the documentation (if applicable)

[timtebeek]

@AlekSimpson As you can see in cb80173 and 6f2b19b I've swapped the logic around to only recognize and apply changes in known cases, rather than what we had previously where might inadvertently make changes by only returning early for known cases. This in my view improves the predictability of the recipe, such that we should be able to safely run it at scale. We now also cover some additional cases, and handle some cases differently, for instance by only retaining the left side of a binary expression, and covering fail(.., Throwable). Hope you agree with those changes, and will apply the same pattern of only making changes for known cases to future recipes.

@joanvr would you be willing to review for a second pair of eyes on my changes?