Please include the config file's name in the error message

### Is your feature request related to a problem? Please describe

This is a paper cut, but I've run into it myself.

In a slack I read, this dialog just took place:

_Person 1:_
I think what I hate the most about asdf is that when it yells at you about needing a config file in a folder but doesn’t tell you the name of the config file
No version is set for command go

```
Consider adding one of the following versions in your config file at
golang 1.17.1
golang 1.19.4
golang 1.20.2
golang 1.20.3
```
endless rage every time

_Person 1:_
it’s apparently .tool-versions, a combination of letters I am guaranteed to get wrong at least three times

_Person 2_
programs that assume you know how the f*** they work kill me

### Describe the proposed solution

The error message should include the name of the file the user is being suggested to edit.

### Describe similar `asdf` features and why they are not sufficient

I'm just asking for a clearer message.

### Describe other workarounds you've considered

Not being clear.

Start by locating the asdf CLI code that produces the “No version is set for command” error and its suggested config-file guidance. Update the resulting message to name the config file, then verify that the displayed guidance clearly tells users which file to edit.

Written by the indexing model from the issue text.