Change Command Failed EVR to Command Severity

[LeStarch]

Currently the Command Dispatcher uses WARNING_HI severity when reporting a command has failed to execute. The proposal is to use the COMMAND severity instead. This is for several reasons:

1. Most users like to see COMMAND severity ... ... ... COMMAND severity blocks in the EVR log to know what time/events the command bracketed. This currently only works when commands succeed.
2. WARNING_HI EVRs typically are used for indicating a cross-component problem. However, a command failure isn't always a problem. Criticality of a command failure is project or component dependent.
3. COMMAND severity EVRs get special GUI processing to replace OpCodes for ease-of-use. This is not applied to WARNING_HI making command failures difficult to diagnose.
4. Most components will report their own more-detailed WARNING_HI EVRs to indicate why a command failed. Having an extra WARNING_HI saying the command failed isn't adding much.

@metzdigital could you elaborate if I missed anything?

[metzdigital]

You've captured the reasons perfectly, thanks @LeStarch!

[LeStarch]

Notes:

• NO_OP testing components should emit appropriate WARNINGs
• Should we emit 2 EVRs WARNING_HI and Command complete: add to checklist, not force warning
• Add to checklist.
• Ensure this only affects properly dispatched commands

[LeStarch]

This one has been approved.