In the case where a Drydock task either fails or times out, it is not very
clear which Drydock task is being referred to. This commit updates the log
messages to include the Drydock task-id that has either failed or timed out.
Additionally, debug logging is added to log the Drydock task status. The reason
for this is because there are situations where a Drydock task is still running,
but on the Shipyard side the task has timed out and therefore, Shipyard shows
the task (i.e. prepare_nodes or deploy_nodes) as failed. It is good to get a point
in time reference to the task state for a couple of reasons:
1) To verify via logging that Shipyard is reporting Drydock tasks (success,
failures, partial_successes, etc) accurately
2) Later on if Drydock shows a node as deployed, then the task can be
queried and the state can be checked to see if the task was indeed a success.
Change-Id: I7050338e2f92ad548e639e2ea4059a520c27e686
1ae9a7c4be