[GR-70201] [GR-68576] Crema: Add support for invokedynamic.

[graalvmbot]

The main goal of this PR is to have java-source-level lambdas and string concatenation working in crema.

• When crema is enabled, don't add digest to lambda names

• Add resolution for INVOKEDYNAMIC entries

  In the RuntimeInterpreterConstantPool, INVOKEDYNAMIC entries are resolved to a ResolvedInvokeDynamicConstant.
  Those hold information about the bootstrap method and a list of call site links. Call site links can either be successful or failed.
  Successful call site links contain an invoker method as well as an appendix.
  The index of the call site link is patched into the 2 empty bytes of the 4 bytes CPI of invokedynamic bytecodes.

• Ignore parallel class loading

  • In order to make progress quickly we are more conservative in how we lock and ignore proper parallel class loading support for now.

• Resolve polymorphic signature methods

• Setup the ability to interpret polymorphic signature intrinsics

  • Polymorphic signature method instantiations have an "intrinsic" field set denoting which kind of intrinsic type it is.
  • The interpreter can dispatch to IntrinsicRoot.execute for intrinsics.
  • Stack walking knows about this interpreter method
  • The special interpreter methods should be marked as @NeverInline and don't need to be added as root.
  • Add support in the interpreter for invokeBasic

• Add a quiet mode for InterpreterToVM.dispatchInvocation

• When enabled, let crema handle MethodHandle, MemberName, & LambdaForm

  In that mode re-enable a number of JDK code path that are usually substituted.

• Add InterpreterUtil.assertion

  This helps avoid AssertionError in the interpreter.

• InterpreterResolvedJavaMethod: make sure some members can't be null.

• InterpreterResolvedJavaMethod: Store internal flags and modifiers in an int

• Crema: detect caller sensitive methods