feat: Better clarity for envd destroy

[AlexXi19]

Description

Using envd destroy incorrectly can be a bit confusing.

Here I was trying to destroy airsolar and the response seemed successful. However, envd_playground was the one that actually got deleted. This can be a bit confusing because the error message shows that the environment is successfully destroyed (even though it's not the right one).

There could be an extra step to determine cases like these where the users are using the destroy command incorrectly and help them notice the error.

---

Message from the maintainers:

Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

[gaocegege]

/cc @kemingy @VoVAllen

[kemingy]

I think it's also related to #1075

[AlexXi19]

To add on to this, deleting non-existent environments can also show success, which can be confusing if you make a typo.

[cutecutecat]

If path and name are not specified either, envd will destroy build.envd at cwd path as default.
This is confiusing, I agree, to let it fail fast here maybe better.

envd/pkg/app/destroy.go

Line 59 in 3c38b5e

path = "."

[hxu296]

Would #1075 be a blocker for this issue? Otherwise I would like to work on this issue :)

I'm learning this codebase and this issue seems to be a good starting point. @gaocegege @cutecutecat

[gaocegege]

Personally, I do not think it is a blocker, WDYT @kemingy @cutecutecat

[kemingy]

It's not blocked but the user experience is affected by #1075.

[gaocegege]

Yeah, that's right.

[hxu296]

Thanks for the prompt response! I will start working on this issue.