Track and list stopped/removed projects, fixes #642

[rfay]

The Problem/Issue/Bug:

Not all projects have been visible to ddev list and related commands. This is a longstanding issue and affects ddev-ui, but is more relevant now that ddev stop actually removes containers, effectively removing ddev's knowledge of the existence of the project.

How this PR Solves The Problem:

• Add stopped projects (which have no containers) to global config, and query from there.

TODO:

• Sort projects by active and then by name
• TestMain must not remove all projects, it needs to just remove projects like "Test*"
• ddev list should probably show only active and paused projects. Add ddev list --all for the rest.
• Need a new ddev stop flag that just stops and removes from global config, doesn't do everything else (nondestructive). Use that in cmd's root_test.go setup so it's not so dangerous.
• Docs:
  • Projects don't get added until they're started once
  • How to delete a project from global config

Manual Testing Instructions:

• Test functionality with ddev-ui if it's still working
• ddev stop -a and ddev list and ddev list --all (which will show stopped/removed projects)
• Start a few projects and ddev list

There are so very many things that can be broken with this (starting/stopping/pausing by name, whether running or not, conflicting stuff in docker from what's in global config). Please spend some serious time poking at it, and trying to make sure you can recreate bugs.

Automated Testing Overview:

• Test for consistency between docker containers and global config project list
• Test for behavior when global projectlist is not fully populated (as will be the case for lots of people)
• Test for situation where there are broken or empty projects in global config

Related Issue Link(s):

OP #642
This should also make ddev-ui work consistently assuming it gets revived.

Release/Deployment notes:

[rfay]

@andrewfrench this is a biggie, requesting some serious look at this from both code and manual testing perspective. Since it changes the whole model from docker-label-query to global-yaml-projectlist, there's just so very much that can go wrong. Thanks for scheduling this in.

[andrewfrench]

Lots of code changes here, which look good to me. I've been testing this manually on and off and have failed to trip it up yet, but I'd imagine we'll be extra vigilant for smaller, hidden regressions between now and release.

[ultimike]

I've been looking forward to this for awhile - I'm sure I've deleted a project's directory or two and forgetting to ddev remove --remove-data along the way.

I've been playing with the alpha 1 version and so far, so good. I haven't run into any issues.

My only comment/request would be that the ddev list --all result be the default. With most folks using a standard ddev start/ddev stop workflow, using ddev list doesn't show anything different. I think it would be super-helpful to show stopped projects by default. Maybe include a ddev list --no-stopped switch or something like that...

-mike

[rfay]

Thanks @ultimike. I think that's a valid request, I thought it would be too big a list for people who work on a lot of projects. Maybe it should go the other way with a --active-only.

[rfay]

#1636 will change the behavior to ddev list shows all projects, ddev list --active-only shows just active. Thanks!