[GR-51059] Resolve configuration conditions during JSON parsing.

[graalvmbot]

Before this PR we were using the following map in ConditionalConfigurationRegistry

public abstract class ConditionalConfigurationRegistry {
    private final Map<String, Collection<Runnable>> pendingReachabilityHandlers = new ConcurrentHashMap<>();

Unfortunately fully qualified Java type names are not suitable as unique keys throughout the lifetime of the analysis. It can easily happen that we have two classes with identical fully qualified Java type names but different meaning because they are coming from two different classloaders.

To correctly adjust to this requirement it means that already on the level of
org.graalvm.nativeimage.impl.ConfigurationCondition there must not be field org.graalvm.nativeimage.impl.ConfigurationCondition#typeName

private final String typeName; 

of type String but instead something like

private final Class<?> type;

consequently the static factory method org.graalvm.nativeimage.impl.ConfigurationCondition#create should be changed as well to only allow creating ConfigurationCondition with actual class objects.

public static ConfigurationCondition create(Class<?> typeReachability) {
    Objects.requireNonNull(typeReachability);
    if (OBJECT_REACHABLE.typeName.equals(typeReachability)) {
        return OBJECT_REACHABLE;
    }
    return new ConfigurationCondition(typeReachability);
}

The only place where it is valid to create ConfigurationCondition from fully qualified Java type names is if we are creating them for json-based configuration entries (e.g. "typeReachable": <fqn> in reflect-config.json).

Key Implementation Notes

The UnresolvedConfigurationCondition is used only during parsing and uses strings to distinguish between types. The ConditionalElement now is also a parsing-only concept.

As a consequence all parsers are now generic in the condition that they use and they accept the ConditionResolver<Cond>.