Sometimes, the bytecode of certain classes are not immediately available within the resources of the system class loader, such as external jar-based plugins. And these code may use APIs that depends on ClassLoader (such as java.lang.reflect.Proxy) or MethodHandles.Lookup for access control, making ClassHierarchyResolver from Reflection based on these two feasible.

Thus, we add two ClassHierarchyResolver::of, one taking ClassLoader and another taking MethodHandles.Lookup, to obtain class hierarchy.

See https://mail.openjdk.org/pipermail/classfile-api-dev/2023-March/000249.html for context.