mml-parser handle obstacles with y=0 correctly

This was breaking the targetGame interactives that had obstacles at y=0 (the top). Classic MW had left these y values unspecified in the mml files, rather than writing out 0. mml-parser was converting missing values to undefined, rather than 0. The parsed obstacles ended up with y=0 (the bottom) in the parsed json file.