RFR: 8297284: ResolutionErrorTable's key is wrong for indy

[Coleen Phillimore]

The resolution error table had a trick for the lookup key of adding constant pool index into constant pool address because that key was assumed to be in the range of the constant pool, so unique.  For failed indy resolution, we also use the resolution error table and the index is not relative to the constant pool, so the key is potentially not unique.  Created a Key class for the table and moved the cpool and index into that.  Now the ResolutionErrorEntry just has the messages.

Tested tier1-4.

-------------

Commit messages:
 - 8297284: ResolutionErrorTable's key is wrong for indy
 - ResolutionErrorTable key not right for indy

Changes: https://git.openjdk.org/jdk/pull/11244/files
 Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=11244&range=00
  Issue: https://bugs.openjdk.org/browse/JDK-8297284
  Stats: 105 lines in 2 files changed: 31 ins; 43 del; 31 mod
  Patch: https://git.openjdk.org/jdk/pull/11244.diff
  Fetch: git fetch https://git.openjdk.org/jdk pull/11244/head:pull/11244

PR: https://git.openjdk.org/jdk/pull/11244