fix: do not validate config in ddev clean, delete -O, stop -U

[stasadev]

The Issue

While testing #6208 I noticed a regression in:

• fix: add project config validation when using args, fixes #5445 #5452
• fix: add config validation for --all flag, for #5452 #5555

ddev config --project-name=d10
ddev config --project-name=d10-rename
ddev config --project-name=d10-rename2
this project root /home/stas/code/ddev/d10 already contains a project named d10. You may want to remove the existing project with "ddev stop --unlist d10"

ddev stop --unlist d10
Project 'd10-rename' was found in configured directory /home/stas/code/ddev/d10 and it is already used by project 'd10'. If you have changed the name of the project, please "ddev stop --unlist d10" 
Failed to get project(s): the d10 project has an invalid hostname: 'd10.', see https://en.wikipedia.org/wiki/Hostname#Syntax for valid hostname requirements

And you are stuck with ddev stop --unlist d10 until you manually clean ~/.ddev/project_list.yaml (or run ddev list)

---

Also the same problem occurs when you are working on some new project type, then you change the DDEV binary and try to delete the test project with this new type, for example, you have foobar type:

ddev delete -Oy
Failed to get project(s): the test project has an invalid app type: foobar

And there is no way to ddev delete -Oy until you fix the config.

How This PR Solves The Issue

Do not run ValidateConfig() on a command with project arguments that don't actually need validation:

• ddev clean
• ddev delete --omit-snapshot
• ddev stop --unlist

The general idea is that we don't need to check the config if we delete something (I think it's annoying, just let me delete it, I don't care), and sometimes users can get stuck in a loop and we don't want that.

---

Allows to delete non-existent projects with ddev delete -O.

Manual Testing Instructions

ddev config --project-name=d10
ddev config --project-name=d10-rename
ddev config --project-name=d10-rename2

ddev stop --unlist d10
Project d10 is already stopped. 
Project d10 has been stopped.

ddev stop --unlist d10-rename
Project d10-rename is already stopped. 
Project d10-rename has been stopped.

# manually edit `type` to something else in .ddev/config.yaml and run
ddev delete -Oy

And check Docker volumes and the contents of ddev-global-cache for:

ddev config --project-name=d10
ddev start
ddev stop --unlist
cd ..

docker volume ls | grep d10

docker run --rm -it -v ddev-global-cache:/mnt/ddev-global-cache ddev/ddev-webserver:v1.23.1 bash
ls /mnt/ddev-global-cache/*/d10-{web,db} /mnt/ddev-global-cache/traefik/*/d10.{yaml,crt,key}

ddev delete -O d10

docker volume ls | grep d10
# should show nothing

docker run --rm -it -v ddev-global-cache:/mnt/ddev-global-cache ddev/ddev-webserver:v1.23.1 bash
ls /mnt/ddev-global-cache/*/d10-{web,db} /mnt/ddev-global-cache/traefik/*/d10.{yaml,crt,key}
# should show nothing

Automated Testing Overview

Related Issue Link(s)

Release/Deployment Notes

[github-actions]

Download the artifacts for this pull request:

• all-ddev-executables.zip
• ddev-linux-amd64.zip
• ddev-linux-arm64.zip
• ddev-macos-amd64.zip
• ddev-macos-arm64.zip
• ddev-windows-amd64-installer.zip

See Testing a PR.

[stasadev]

I'm not sure, but maybe we don't need the validation in ddev delete and ddev stop at all.
Let me know if I need to change anything.

[rfay]

I would like ddev delete to delete related volumes even if the project can't be validated or doesn't exist any more. For example, ddev delete -Oy tempproj should kill off volumes that would have been for tempproj and probably things in ddev-global-cache even if the files had long since been removed. This doesn't necessarily belong in this PR, but you asked :)

[stasadev]

I would like ddev delete to delete related volumes even if the project can't be validated or doesn't exist any more.

Good idea and doesn't require much change, done.

[rfay]

Rebased. I was testing and the problems mentioned in the OP are gone... because #6208 was fixed :)

[stasadev]

Yes, that's right, now you have to manually break the config.

[rfay]

This seems like a really nice improvement, thanks! This has been a piece of friction for DDEV users for a long time. And allowing deletion of non-existing projects (getting rid of their databases and mutagen state) has been on my personal to-do list for some time.