Better error message when finding lingering `.workspace` file after an app delete

[Lou1415926]

When customers run copilot app delete, Copilot will delete all the application resources, as well as the .workpace file under copilot/ folder.

However, there are times when customers perform manual deletions instead of copilot app delete, or something interrupted during the execution of copilot app delete. These may end up in a state where the app has actually been deleted, but the .workspace file lingers. #3262 is an example. This may bring confusion to customers.

I proposal Copilot surface better error message / recommended actions when:

1. It's found a .workspace file
2. It is not able to find the application indicated by the .workspace file

In this case, we can provide recommended actions:

1. To suggest deleting .workspace file if customer knows they've attempted to app delete before app init
2. Suggest switching region otherwise.

[arferreira]

Hello @Lou1415926, this issue still is open?
I would like to work that.

[iamhopaul123]

Hello @arferreira. It is still open but we are still thinking about if this is the best way of solving this problem. In the meanwhile, would you mind picking up other issues labeled with "good first issue"?