MSPA US National String Hardcodes V1 but returns V2 length strings

[jwkosten]

For MSPA US National String V1 the following fields should have the corresponding lengths

SensitiveDataProcessing | N-Bitfield(2,12)
KnownChildSensitiveDataConsents | N-Bitfield(2,2)

When the strings are generated in the UI, they return strings where the following fields have length

SensitiveDataProcessing | N-Bitfield(2,16)
KnownChildSensitiveDataConsents | N-Bitfield(2,3)

This would be valid if the version was set to 2, however the GPP site hardcodes the version for each MSPA string to 1.