container logs not flushed if there is a timeout spinning up a container

#392 added a ContainerStop to Deployer.Destroy, so that the container has a chance to gracefully shut down and flush its logs before we print them.

However, we print the logs in a couple of other situations:

• in Deployer.Deploy, if there is a timeout waiting for the container to be ready. (In this case it looks like we don't destroy the container at all?)
• in Builder.ConstructBlueprint (via Builder.construct).

In both these cases, the logs are printed before the container is stopped.

Inizia leggendo Deployer.Deploy e Builder.ConstructBlueprint tramite Builder.construct, quindi confronta la loro gestione dei log con Deployer.Destroy e il relativo comportamento ContainerStop. Riproduci i percorsi di timeout e di costruzione per verificare quando vengono stampati i log. Il lavoro è completo quando il container viene arrestato prima della stampa dei log in entrambi i casi e il percorso di timeout gestisce correttamente anche il ciclo di vita del container.