Do not add nullable annotations for computeIfAbsent/Present

Lead to excessive nullable annotations and warnings that in practice could not happen unless the computed value was null.

src/main/java/org/openrewrite/staticanalysis/AnnotateNullableMethods.java

@@ -29,6 +29,7 @@
 import java.util.Arrays;
 import java.util.Comparator;
 import java.util.List;
+import java.util.Map;
 import java.util.concurrent.atomic.AtomicBoolean;
 
 public class AnnotateNullableMethods extends Recipe {
@@ -83,13 +84,16 @@ public J.MethodDeclaration visitMethodDeclaration(J.MethodDeclaration methodDecl
     private static class FindNullableReturnStatements extends JavaIsoVisitor<AtomicBoolean> {
 
         private static final List<MethodMatcher> KNOWN_NULLABLE_METHODS = Arrays.asList(
-                new MethodMatcher("java.util.Map computeIfAbsent(..)"),
-                new MethodMatcher("java.util.Map computeIfPresent(..)"),
+                // These mostly return a nullable current or  previous value, which is more often null
                 new MethodMatcher("java.util.Map get(..)"),
                 new MethodMatcher("java.util.Map merge(..)"),
                 new MethodMatcher("java.util.Map put(..)"),
                 new MethodMatcher("java.util.Map putIfAbsent(..)"),
 
+                // These two return the current or computed value, which is less likely to be null in common usage
+                //new MethodMatcher("java.util.Map computeIfAbsent(..)"),
+                //new MethodMatcher("java.util.Map computeIfPresent(..)"),
+
                 new MethodMatcher("java.util.Queue poll(..)"),
                 new MethodMatcher("java.util.Queue peek(..)"),