Define a base and derived deserializer class

[cjjdespres]

The JITServerAOTDeserializer is now two classes. The base JITServerAOTDeserializer defines some common operations and functionality, and the derived JITServerLocalSCCAOTDeserializer implements the required deserialization and caching.

[cjjdespres]

Attn @mpirvu. This could be the basis of keeping the old deserializer implementation around. In #18301 I could create something like a -XX:[+|-]JITServerAOTCacheIgnoreLocalSCC option. If enabled, we would, among other things, use a new deserializer (called JITServerNoSCCAOTDeserializer or something). If disabled, we'd still use the old JITServerLocalSCCAOTDeserializer.

I initially tried having just a single JITServerAOTDeserializer class that could do one or the other, but what exactly they cache and how they validate certain things is different enough that having a few different derived implementations of a base interface seemed a lot cleaner. (Having a single class would make it easier to, say, fall back to the new implementation if we were using the old implementation and the SCC filled up, but that would bring its own complexity and I don't think we want to support that anyway).

[mpirvu]

LGTM

[mpirvu]

jenkins test sanity plinuxjit,xlinuxjit,zlinuxjit,alinux64jit jdk17