TEDEFO-5239 Provide the typed attribute and the code list of each data type

[rousso]

The attribute and the code list of each data type

TEDEFO-5239

To display the unit of an amount, a measure or a duration in a format block, the EFX Toolkit needs to know which attribute of a field holds the unit. For a calculated duration, which has no field, it needs the code list of its unit. Until now, it had to hard-code both.

Each SdkDataType now has:

• getAttributeName(): the attribute that the fields of the type carry, for example currencyID for an amount;
• getAttributeType(): the data type of that attribute, for example currency;
• getListName(): for the four new data types currency, measurement-unit, duration-unit and language, the root code list of their values, for example timeperiod for duration-unit.

The code list of the unit of a calculated duration is therefore the list name of the type of the attribute of duration: timeperiod. For a field, the code list of its unit still comes from its attribute field in fields.json. The design is in section 6 of eForms Data Types.

The data types now follow the pattern of the other SDK entities:

• SdkDataTypeV1 and SdkDataTypeV2 are created by SdkEntityFactory.getSdkDataType(sdkVersion, JsonNode), from an entry in the format of fields/fwd/data-types.json.
• SdkDataTypeRepository(sdkVersion) reads them from a data-types.json resource of this library, in that format. SDK 1 has no such file, so this is where its data types come from. Reading the SDK 2 file is left to TEDEFO-5231, once it has the four new data types and the types of the attributes (TEDEFO-5238), and the masking value of duration (TEDEMD-1117).
• createDefault() is unchanged, and deprecated.

Validation

• New SdkDataTypeRepositoryTest: 9 tests.
• mvn verify: all 100 tests pass, and so does the API compatibility check.