Confusing/improper behavior on "ddev rm" when db container is broken

[rfay]

Describe the bug

If the db container is broken (won't come up, usually due to corrupted database) and you get "db service stopped" on ddev list then:

ddev rm --R may fail with confusing errors where it immediately starts the project (to make a snapshot, but it hasn't said that yet). During the start, it fails, and never gets to the snapshot.

To Reproduce

1. Make a snapshot of the good db
2. Break a project's db container. ddev ssh -s db and rm /var/lib/mysql/mysql/*.MYD and ddev restart. ddev list should show "db container stopped". Pretty nasty thing to do to a database.
3. ddev rm -R.

Result is

$ ddev rm -R
Starting ddev-t3git-db ... done
ddev-t3git-dba is up-to-date
ddev-t3git-web is up-to-date
Stopping ddev-router ... done
Removing ddev-router ... done
Network ddev_default is external, skipping
Creating ddev-router ... done

and ddev list shows just "db container stopped" again. No hint is given of what the problem or procedure is.

ddev rm -R --omit-snapshot solves the problem just fine.

Expected behavior

I expect ddev rm -R to always succeeed. It should probably just warn if a snapshot can't be created and continue to removal. It's also questionable whether we should always be creating the snapshot. Maybe we should ask.

Version and configuration information (please complete the following information):
ddev v1.2.0

Additional context
Add any other context about the problem here. Thanks!