ezrassor_configurable_simulation: control_methods:=autonomy should imply control_methods:=keyboard

[CSharpRon]

When only the autonomy control method is defined, the system should be ready to accept keyboard commands by default when no other control method is listed. Alternatively, we can make a control_method required and split autonomy into its own argument i.e., autonomy_enabled:=true.

This is an issue because it impacts usability. Users may think that just by defining autonomy, the system will automatically start.

Additionally, we should print a message to roslog telling the user what to do to start the autonomy commands.

Possibly tied to #358