Minor - odd order of output from cylc stop --max-polls command

[ColemanTom]

Description

I noticed a fairly cosmetic (in my opinion) bug with cylc stop --max-polls. It does not print out the command queued until after everything is stopped.

e.g.

$ cylc stop --max-polls=10 --interval=10 --kill handler/run2 basic-workflow/run1
.
..
handler/run2: Command queued
basic-workflow/run1: Command queued

Reproducible Example

1. Launch two workflows
2. Run cylc stop --max-polls=10 --interval=10 first second
3. See the output

Expected Behaviour

I would have expected the command queued to be printed out immediately, and then the .'s.