Relax the invokespecial lookup

Account for the fact that invokespecial dispatches mostly dynamically
for super method calls

core/src/main/kotlin/com/toasttab/expediter/Expediter.kt

@@ -183,9 +183,9 @@ private class MemberWithDeclaringType(
 )
 
 private fun ResolvedTypeHierarchy.CompleteTypeHierarchy.filterToAccessType(access: MemberAccess): Sequence<Type> {
-    return if (access is MemberAccess.MethodAccess && access.accessType == MethodAccessType.SPECIAL) {
-        // invokespecial dispatches statically, i.e. the method must be declared on the target type;
-        // it is used to invoke constructors, super methods, and private methods
+    return if (access is MemberAccess.MethodAccess && access.accessType == MethodAccessType.SPECIAL && access.ref.isConstructor()) {
+        // when invoking constructors, invokespecial dispatches statically
+        // when invoking super methods, invokespecial dispatches mostly dynamically
         sequenceOf(type)
     } else {
         // fields and methods, except for constructors can be declared on any type in the hierarchy

tests/src/testFixtures/java/com/toasttab/expediter/test/caller/CallerNegative.java

@@ -20,10 +20,11 @@
 import java.lang.invoke.MethodType;
 import java.lang.invoke.VarHandle;
 import java.util.Arrays;
+import java.util.LinkedHashMap;
 import java.util.List;
 import java.util.SortedSet;
 
-public class CallerNegative {
+public class CallerNegative extends LinkedHashMap {
     private int x;
 
     void arrayCloneIsOk() {
@@ -86,4 +87,9 @@ void varHandle() throws Throwable {
 
         vh.get(new int[0]);
     }
+
+    void superSuperCallOk() {
+        // `invokespecial LinkedHashMap.remove(Object)` should be ok even though `remove` is declared on `HashMap`
+        super.remove(new Object());
+    }
 }