glyphs2ufo produces different results than fontmake -o ufo

I noticed that, when generating UFOs of an Italic Glyphs source, I am seeing different results in the UFO generated. This is causing the variable fonts that I eventually produce to lack Italic classification in the fsSelection and macStyle bits.

In particular the difference is being caused by the lack of styleMapFamilyName / styleMapStyleName in the master UFOs being produced.

Here are the fontinfo files produced by the two methods, and the glyphs file from which they were generated:
[Archive.zip](https://github.com/googlefonts/glyphsLib/files/11127794/Archive.zip)

For reference, here's the versions of glyphsLib and fonttools I have installed:
glyphsLib 6.0.7
fonttools 4.39.2

The fontmake output appears to be the better approach for generating UFOs that will eventually be built using fonttools, so that's what I have implemented, but I was surprised to see the difference.

Any idea what might be going on here?

Start by unpacking Archive.zip and comparing the fontinfo files produced by glyphs2ufo and fontmake, along with the source .glyphs file. Trace how the two commands populate styleMapFamilyName and styleMapStyleName, then verify that the generated master UFOs preserve Italic classification in the downstream fonttools output.

Written by the indexing model from the issue text.