Improve startup feedback when container is being pulled

[afscrome]

When a container is being pulled for the first time, the resource remains in the "starting" state on the aspire dashboard, without any indication of why the resource is taking so long to start up. That can sometiems take a long time for a large image and/or slow network connection.

It would be helpful to have some indication that the image is being pulled - perhaps something in the resource logs?