Allow User-Specified Commands to be sent from Flight Software

[epdalessandro]

In the component queue there are annotations on each port (drop or assert) to specify whether to drop an overflowing message or assert fatally, giving the user the power to define behavior on a port-by-port basis.

Like this annotation I would propose having a command definition file or add annotations to commands that would specify whether or not the command could be sent from both the GDS and flight software (i.e. a component could send a command) or only allow the GDS to send the command as is currently the case. This could be implemented by either allowing components to trigger a command like the GDS does, or by automatically creating ports between the components with the same arguments that the command sends, as a command-proxy.

I came across this idea as we won't have a direct connection with our ground station since we need to go through a python layer with our radio, and so build-in functionality to allow the component responsible for interfacing with the radio to send commands to the rest of the components would be very useful, rather than manually specifying port connections between that component and each of the others that need to receive commands.

Any thoughts would be appreciated!