commands: Always NUL terminate command buffer

Since we pass the buffer to the process_external_command1() routine
regardless of whether it seems well-formed or not, we better terminate
it regardless as well. If we don't, we're going to overread the buffer
sooner or later, causing not only this but also subsequent commands to
become garbled.

This fixes op5#8682.

Signed-off-by: Anton Lofgren <alofgren@op5.com>
Merge pull request #62 from catharsis/terminate-command-buffer

commands: Always NUL terminate command buffer