Make ddev logs work against stopped project/container, fixes #719

[rfay]

The Problem/Issue/Bug:

OP #719: Currently ddev logs only works against running containers, so is useless when trying to debug a stopped container (perhaps stopped for a healthcheck failure). This commonly happens when people add custom config that is broken. But then ddev logs doesn't help them and we have to coach them on using the more arcane docker logs options.

How this PR Solves The Problem:

There was an explicit stanza that forbade getting logs on stopped containers. Remove it.

Manual Testing Instructions:

• Start a project
• Stop the project
• Run ddev logs and ddev logs -s db to see the logs from the project.

Automated Testing Overview:

I didn't add anything.

Related Issue Link(s):

OP #719

Release/Deployment notes:

[rickmanelius]

I did a test with v0.17.0 and this PR. I can confirm that it wasn't working before (with v0.17.0 I received a message that the project was stopped), but with the PR I get the same results as when the container is running.