Current implementation of MemberName::resolveOrNull defers to MethodHandleNatives::resolve, which provokes exceptions when the member name being resolved does not exist.

Providing a resolveOrNull on MHN would allow using MN::resolveOrNull speculatively without losing performance, while improving performance for cases which already does this.