This issue is to add basic support to JVMCI for CONSTANT_Dynamic constant pool entries. It will bring the JVMCI support on par with the support in CI for C1 and C2. It will differ a bit from CI support in that JVMCI will resolve unresolved condy entries (CI bails out in this case as it expects condy entries to be resolved by the interpreter).

When using JVMCI for JIT compilation, unresolved entries should only be seen when running under -Xcomp.

When using JVMCI for AoT (e.g. Native Image), most entries will be unresolved since no other code apart from the AoT compiler is running.

A follow on issue will investigate using the ConstantDesc API (JDK-8210031) to allow JVMCI constant pool entries to be resolved to their nominal form. AoT can then use analysis and/or external configuration to decide which condys should be resolved during AoT and which should be resolved at runtime.