Presentation of redefined attributes types in objects is incorrect

[rmouritzen-splunk]

In cases where an object attribute's type is redefined or refined by specifying a value for type that is different than the dictionary's type, and a caption attribute is no also supplied, the type name shown in the "Type" column for the attribute on the object's page -- at the /objects/:id URL -- incorrectly shows the type name from the dictionary and not the type name associated with redefined type.

Example:
The presentation of the Fingerprint object's type in the "Type" column on the /objects/fingerprint page incorrectly shows the type name "String" -- the type of value in the dictionary. The Fingerprint object refines the type of value to file_hash_t, which has a type name of "Hash" in the dictionary.

Note: The human-readable type_name is incorrect. The actual type in the type property is correct. This (probably) only affects how the OCSF Server presents this information. Other uses (hopefully) only use the type property.

The suspected cause is that the "simple" folding of the dictionary and object type information is not handling this edge case. In most cases, types are not refined / redefined in object definitions.

Cases where this happens in the 1.2.0-dev schema (most or perhaps even all of these exist in prior versions as well):

• Fingerprint.value -- redefined as file_hash_t
• File.name -- redefined as file_name_t
• User.name -- redefined as username_t