Windows platform fonts may be incorrectly marked as ineligible for the native rasteriser

JDK uses Windows to rasterise LCD glyphs for Windows installed TrueType fonts
when there is a simple transform on the font.
It uses JDK's rasteriser for all other scenarios (non-LCD, or JRE or
non-installed fonts, rotation transforms etc, or any other platform except Windows).

On creation of the internal font object its marked as to whether its
eligible to be used via the native rasteriser or should always use the
Java one. This is typically based on the location (path name) of the font.

However "6795908: Refactor FontManager" in JDK7 b74 lost this logic
in one place which appears to affect all fonts referenced in the
font config files such that they will always use the Java rasteriser.

However much of this appears to be masked in Font2DTest or other
cases where we locate all the fonts because the fontconfig file
uses upper case names and the registry look up returns lower case
names and we apparently overwrite the first font.

But all of this needs to be fixed.