@chuff can you please describe how this broke and why this works in the pr description

Yeah, basically when DE, IA, NE, NH, NJ, TN was released, USNAT was updated to accommodate 4 additional values for sensitive data processing and 1 additional value for known child sensitive data consents. Since those 2 fields are not at the end of the string, to maintain backwards compatibility, a check needs to be done to see if the string to be parsed was created before or after this change. Since string length is a consistent identifier, I chose that option and injected default values into the string at the correct locations for the newer values.