`turso db destroy --instance` gives misleading error message when given a non-existent database

[CodingDoug]

If I issue a command targeting a database that doesn't exist:

$ turso db destroy non-existing-db --instance existing-instance-elsewhere
Error: instance not found

The error suggests that the named instance did not exist in the database, but it's the entire database that didn't exist. The error message could be more clear what specifically was not found.

Good general improvements would be:

• Replacing all error messages resulting from database not found to suggest using turso db list to find the ones that do.
• Replacing all error message resulting from a specific instance not found to suggest using turso db show existing-db to find the ones that do.

[haaawk]

I think the error isn't incorrect. There is no existing-instance-elsewhere instance in non-existing-db and the fact that existing-instance-elsewhere exist in another database is not important. Instance X in database A is different than instance X in database B.

I do agree that pointing out that the db name is wrong is a better error though.