[NativeAOT] Improve managed type map

[simonrozsival]

This is a follow-up to #9856

#9846 showed that several tests are failing with the new managed type map. This PR addresses two of these issues:

1. Use assembly qualified type name instead of just full name for the managed -> Java mapping
2. Handle generic types correctly:
   • for managed -> java mapping, include all the different types which map to the same java class name (e.g., JavaList and JavaList<object> both map to java/util/ArrayList)
   • for java -> managed mapping, prefer non-generic base classes over generic subclasses (e.g., map java/util/ArrayList to JavaList instead of JavaList<>)

These changes now break roundtripping (JavaList<T> -> java/util/ArrayList -> JavaList). This broke the current way of checking for hash collisions. I haven't figured out a good way to replace these checks. Since we aren't checking hash collisions in native type maps, maybe we don't need to do the collision checks in the managed type map either.