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.

まず Builder.construct を介した Deployer.Deploy と Builder.ConstructBlueprint の処理を読み、次にそれらのログ処理を Deployer.Destroy とその ContainerStop の動作と比較します。ログがいつ出力されるかを確認するため、タイムアウト経路と構築経路を再現します。両方のケースでログが出力される前にコンテナが停止され、さらにタイムアウト経路でもコンテナのライフサイクルが正しく処理されれば完了です。