InSAR Metadata Discrepancies

I ran nisarqa's XML Checker on recent InSAR granules. I submitted a PR to isce3 and a PR to PIX product spec repo which resolve many of the discrepancies.

There are a few remaining items:

RUNW, GUNW:

• "XML expects string. HDF5 has type object, but should be a NumPy byte string. Dataset /science/LSAR/RUNW/metadata/processingInformation/algorithms/ionosphereEstimation/ionosphereOutliers"

GUNW:

• "Attributes found in XML but not HDF5: {'disclaimer', 'valid_min'} - Dataset /science/LSAR/GUNW/grids/frequencyA/unwrappedInterferogram/mask"
• "Attributes found in XML but not HDF5: {'valid_max', 'disclaimer', 'valid_min'} - Dataset /science/LSAR/GUNW/grids/frequencyA/wrappedInterferogram/mask"

ALL FIVE:
These additional errors are similar to ones found in RSLC (See: #202 ). Could you please confirm that InSAR workflows will automatically inherit the fixes from RSLC, once focus.py is updated?

• "dtypes differ. XML: uint8, HDF5: uint32 - Dataset /science/LSAR/identification/diagnosticModeFlag"
• "Attributes found in HDF5 but not XML: {'units'} - Dataset /science/LSAR/identification/referenceAbsoluteOrbitNumber"
• "Differing units attributes detected for datasets. XML: None, HDF5: 'unitless': Dataset /science/LSAR/identification/referenceAbsoluteOrbitNumber"
• "Attributes found in HDF5 but not XML: {'units'} - Dataset /science/LSAR/identification/secondaryAbsoluteOrbitNumber"
• "Differing units attributes detected for datasets. XML: None, HDF5: 'unitless': Dataset /science/LSAR/identification/secondaryAbsoluteOrbitNumber"

cc: @bhawkins @hfattahi