Fix repoquery issues

[Hind-M]

Fix #2320 items

[JohanMabille]

After the review, I was wondering: should we switch to use_local automatically when the channels are empty, and warn the users? This will simplify the logic (no need for an additional option in the command line for instance).

Or do we want to give the user the ability to use the local packags only even if a channel(s) is (are) provided?

[Hind-M]

After the review, I was wondering: should we switch to use_local automatically when the channels are empty, and warn the users? This will simplify the logic (no need for an additional option in the command line for instance).

Or do we want to give the user the ability to use the local packags only even if a channel(s) is (are) provided?

Hmm I think that there is a case where the channels can be configured using a rc file or other config sources, and the user may want to choose to use local repoquery for installed packages or remote (--channel option is not given by the user either way but in case of --use-local=0, the configured channels would be used).

[jaimergp]

The extra message is breaking the JSON output in my dev environment :(

{
    "query": {
        "query": "conda >23.1.0",
        "type": "search"
    },
    "result": {
        "msg": "No entries matching \"conda-forge::conda>23.1.0\" found",
        "pkgs": [],
        "status": "OK"
    }
}conda-forge::conda>23.1.0 may not be installed. Try specifying a channel with '-c,--channel' option

Parsing this blindly gives json.decoder.JSONDecodeError: Extra data: line 11 column 2 (char 223)