Avoid creating reflection entries for java and primitive types.

[christophstrobl]

This commit fixes an issue where the JPA processor inspects too many types for potential reflection configuration. We now skip types within the java namespace as well as primitives and primitive arrays.

[sdeleuze]

@schauder I am hesitant about what is the right behavior for JPA native reflection configuration for Java/primitive types. Currently it provide full reflection for all methods/constructors/fields of java.* types, that's too much for sure. But should we skip those totally or just configure reflection on related class without methods/constructors/fields flags (depending on what JPA/Hibernate require)?

[schauder]

This seems appropriate to me. I find it highly unlikely that Hibernate (or any other JPA implementation) uses reflection to access java.* classes via reflection. I would expect them to do just a type check and then cast accordingly which also should make Graal include the respective class in the binary.

Of course, there is always the risk that Hibernate does something evil with some special type, but if that is the case I think our only chance is to find it via a bug report.