RFR: 8301996: Move field resolution information out of the cpCache [v12]

[Matias Saavedra Silva]

> The current structure used to store the resolution information for fields, ConstantPoolCacheEntry, is difficult to interpret due to its ambigious fields f1 and f2. This structure can hold information for fields and methods and each of its fields can hold different types of values depending on the entry type.
> 
> This enhancement introduces a new data structure that stores the necessary resolution data in an intuitive an extensible manner. These resolved entries are stored in an array inside the constant pool cache in a very similar manner to invokedynamic entries in JDK-8301995.
> 
> Instances of ConstantPoolCache entry related to field resolution have been replaced with the new ResolvedFieldEntry. Verified with tier 1-9 tests. 
> 
> This change supports the following platforms: x86, aarch64, PPC. and RISCV

Matias Saavedra Silva has updated the pull request incrementally with one additional commit since the last revision:

  Fix tos_state

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

Changes:
  - all: https://git.openjdk.org/jdk/pull/14129/files
  - new: https://git.openjdk.org/jdk/pull/14129/files/14e8297d..a090b482

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jdk&pr=14129&range=11
 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=14129&range=10-11

  Stats: 5 lines in 2 files changed: 0 ins; 0 del; 5 mod
  Patch: https://git.openjdk.org/jdk/pull/14129.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/14129/head:pull/14129

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