Use Runnable in functional method test

Update `MethodUtilsTest#testFindFunctionalInterfaceMethod` to validate against `Runnable#run` instead of `Consumer#accept`, and remove the now-unused `Consumer` import. This keeps the test focused on a no-arg functional interface method while preserving existing non-interface and non-functional interface assertions.

Author: mercyblitz

microsphere-java-core/src/test/java/io/microsphere/reflect/MethodUtilsTest.java

@@ -32,7 +32,6 @@
 import java.util.EventListener;
 import java.util.List;
 import java.util.Objects;
-import java.util.function.Consumer;
 import java.util.function.Predicate;
 
 import static io.microsphere.AbstractTestCase.JACOCO_AGENT_INSTRUCTED;
@@ -634,8 +633,8 @@ void testFindNearestOverriddenMethodOnObject() {
 
     @Test
     void testFindFunctionalInterfaceMethod() {
-        Method method = findMethod(Consumer.class, "accept", Object.class);
-        assertEquals(method, findFunctionalInterfaceMethod(Consumer.class));
+        Method method = findMethod(Runnable.class, "run");
+        assertEquals(method, findFunctionalInterfaceMethod(Runnable.class));
 
         // non-interface type
         assertNull(findFunctionalInterfaceMethod(Object.class));