XTCE13 — Mistake in AlarmType refactoring

It appears that when several base alarm types were made (BooleanAlarmType, BinaryAlarmType, EnumerationAlarmType, NumericAlarmType, etc) that the BinaryAlarmType did not get completely applied. This only affects the class hierarchy when using a code generator and does not affect user documents.

This "BinaryContextAlarmType" should have called out xtce:BinaryAlarmType as the extension instead of xtce:AlarmType:

<complexType name="BinaryContextAlarmType">
<complexContent>
<extension base="xtce:AlarmType">
<sequence>
<element name="ContextMatch" type="xtce:ContextMatchType"/>
</sequence>
</extension>
</complexContent>
</complexType>

Propose to correct minor class inheritance on BinaryContextAlarmType

Propose to adjust the following type to leverage the class inheritance that was intended by a previous change. This makes it match the others and does not affect the actual XTCE compliant documents.

Existing BinaryContextAlarmType:

<complexType name="BinaryContextAlarmType">
<complexContent>
<extension base="xtce:AlarmType">
<sequence>
<element name="ContextMatch" type="xtce:ContextMatchType"/>
</sequence>
</extension>
</complexContent>
</complexType>

Should be:

<complexType name="BinaryContextAlarmType">
<complexContent>
<extension base="xtce:BinaryAlarmType">
<sequence>
<element name="ContextMatch" type="xtce:ContextMatchType"/>
</sequence>
</extension>
</complexContent>
</complexType>