Update switch documentation to clarify most calls are for a job step

Rather than a job
Srun to keep running after receiving unrecognized message

This can happen if something outside of Slurm opens the srun socket
and writes to it, since the data will not be of a form that Slurm
can decode.
Bug 354