Non-entity classes in persistence.xml

Listing a class without persistence metadata in a persistence unit (class element) previously failed at start-up with "No registered metadata for type", in the runtime enhancer, in getMetamodel() and during schema synchronization. Such a class is now skipped instead, because a persistence unit may legitimately list classes that are not managed types. The skip is logged as a warning on the openjpa.MetaData log when the metamodel is built and on the openjpa.jdbc.Schema log during schema synchronization, so a forgotten @Entity annotation remains diagnosable.

Note that with the default openjpa.RuntimeUnenhancedClasses=unsupported such a class is still rejected at start-up, by the runtime enhancer, with "This configuration disallows runtime optimization"; the skip described above applies once that check passes.