3.1r1: section 10, output control events

[jadamcrain]

Adds 3.1r1's section 10, for a device whose Device Profile claims output events.

• 10.3.2, 10.4.2: output status in class 0, wherever the DUT has the events.
• 10.3.3, 10.4.3: output status events on a change of each flag the plugin can change, with nothing else changed, and of state or value where the DUT reports those.
• 10.3.4, 10.4.4: output command events, for a command that succeeds and for one that doesn't (analog in g43v2 or g43v4).
• Events are counted from the object headers, so command events, which carry no measurement, count too. The status event tests change back the flags they changed, also when a step fails.
• Options say which output events the DUT has (supports.binaryOutputCommandEvents, supports.analogOutputCommandEvents), which flags the plugin can change, whether state or value changes generate events, the analog output deadband, and whether a command resets its base. Values the tests apply stay within 16 bits; step 27's command differs by the deadband plus 10 from the value step 4 recorded.
• 10.4.2's step 2 names object 10 variation 2 where its desired behavior has analog output status, g40v2, which the test reads.
• Codec and plugin. dnp3c gains a codec for binary output command events (group 13). IntegrationPlugin gains changeOutputFlag, changeBinaryOutputState, setAnalogOutputValue and verifyCommandEventTime, with throwing defaults.