[tx] Move FDArray from fontinfo.plist to lib.plist

[kaydeearts]

[lgtm-com[bot]]

This pull request introduces 1 alert when merging 2db3a0fc75b332b9bd9fff13dfbf155a3b58b9a7 into 5717e38bf7395f4cc5ac567cb05297b28d4cfc74 - view on LGTM.com

new alerts:

• 1 for Missing return statement

[punchcutter]

After looking at https://github.com/adobe-type-tools/afdko/issues/1396 I wonder did we up the version numbers for anything yet?

[kaydeearts]

@punchcutter In my new commits I bumped the version numbers & fixed uforead for non-cid-keyed UFOs with glifs named cidXXXXX. I added a test for it too, does that test reflect the same issue you ran into?

[punchcutter]

tx on this UFO fails with a segmentation fault because of the <integer> in lib.plist here:

    <key>designspace.location</key>
    <array>
      <array>
        <string>weight</string>
        <integer>95</integer>
      </array>
    </array>

If I move this section to a different location it will work fine, but right after FSType or Supplement will fail because those are also expecting <integer>.

Another issue is the warning tx: (ufr) Warning: glyph order does not contain glyph name 'cid00000' for every glyph in the font because the public.glyphOrder gets written at the end of the file and we are expecting to have read it first.

cidtest-ExtraLight.ufo.zip

[kaydeearts]

Changes in this PR will need to be redone due to the replacing tx parser with libxml2 project. Keeping this as reference for when I work on this on a new branch.

[kaydeearts]

Closing due to #1576 completing this work.