Master logs of integration commands are confusing about bst-staging HOT 3 CLOSED

commit 01fd7dfc0497121ef544fc4c86a7b547260d933e
Author: Tristan Van Berkom <tristan.vanberkom[[Gitlab user @codethink]](https://gitlab.com/codethink).co.uk>
Date:   Wed May 24 18:15:23 2017 +0900

    widget.py: Only print the task elements in the output
    
    This could be further enhanced to also print the originating
    element whenever message.task_id != message.unique_id, but for
    now this is better.

commit ec756fb252ecd6a1c30beb994701f454f6ef9310
Author: Tristan Van Berkom <tristan.vanberkom[[Gitlab user @codethink]](https://gitlab.com/codethink).co.uk>
Date:   Wed May 24 18:15:06 2017 +0900

    _scheduler.py: Tag messages sent to the frontend with the task_id

commit ae08f92b748f1025b5791ebbb1ebaea5a7f7d0b8
Author: Tristan Van Berkom <tristan.vanberkom[[Gitlab user @codethink]](https://gitlab.com/codethink).co.uk>
Date:   Wed May 24 18:14:02 2017 +0900

    _message.py: Added task_id parameter
    
    To differentiate between the element and the task, some messages come
    from an element that is not the primary element of the task (i.e.
    when running integration commands on behalf of another element)