!w command does not give any response if a job is in queue and not assigned to a worker/pipeline #292

The responses given by the !w command are inconsistent:

If job is nonexistent:
!w <nonexistent_job_id> gives a response of:
nickname: Sorry, I don't know anything about <nonexistent_job_id>.

If job exists and is assigned to a pipeline already:
!w <active_job_id> gives a response of:
nickname: Job <active_job_id> is on pipeline "<pipeline_name>" (pipeline:<pipeline_hash>).

However, if a job is queued, the command yields no response at all:
!w <queued_job_id> gives no response.

in this case, !status <queued_job_id> responds:
nickname: Job <queued_job_id> <<queued_url>>:
nickname: Started by <job_starter_nickname>.
nickname: In queue.

I recommend it should respond to !w in this case anyway, but give a response something like:
nickname: Job <queued_job_id> is in the queue and has not yet been assigned to a pipeline.