Better restrict domains for Echelon/Mobility and Status (2525C/2525B/APP6B)

[csmoore]

A few of the field attributes in the legacy standards could have better restricted domains for the Echelon/Mobility and Status fields.

For example, this unit echelon field should not include the domain values for mobility since they do not apply to units (only equipment). Conversely, the equipment field should not have the echelon values.

A similar situation exists for the Control Measures Status field (2525C/B only). The control measures show the Operational Condition (damaged/destroyed/etc) that only apply to non-control measures.

The solution would be to create 2 separate domains and attached these new domains to these fields. Applies to fields: echelonmobility, status. Applies to standards 2525C/2525B/APP6B

Screenshots showing issue:

Unit domain values (should not have mobility values):

Equipment domain values: (should not have echelon values)

Control Measure Status (should not have operational condition values):

This issue was noted in #373 (comment)