XTCE13 — needs to be updated for items that no longer support hex, octal, binary

Items that previously were typed as FixedIntegerValueType but were changed to become long need to be revisited to update the documentation annotation. For instance IntegerDataType initialValue attribute documentation:
"Default/Initial value is always given in calibrated form. Default is base 10 form; binary, octal, or hexadecimal values may be given by preceding value with 0[b|B], 0[o|O|, 0[x|X] respectively."
Such forms no longer validate against the schema.

Fix the Parameter/Argument IntegerDataType base 10 documentation miss

In the schema complexType IntegerDataType, there is an attribute named initialValue:

<attribute name="initialValue" type="long">
<annotation>
<documentation xml:lang="en">Default/Initial value is always given in calibrated form. Default is base 10 form; binary, octal, or hexadecimal values may be given by preceding value with 0[b|B], 0[o|O|, 0[x|X] respectively.</documentation>
</annotation>
</attribute>

The intention in XTCE 1.2 was to remove the capability to use the binary, octal, and hex flexibility for specifying the number. In XTCE 1.2, we failed to remove this from the documentation element.

Modify the attribute to be defined as:

<attribute name="initialValue" type="long">
<annotation>
<documentation xml:lang="en">Default/Initial value is always given in calibrated form. Specify the value as a base 10 integer.</documentation>
</annotation>
</attribute>

For the parallel type, ArgumentIntegerDataType, also apply the identical attribute block replacing the initialValue attribute.