[feature] Implement verbosity levels for 'remote' command

[cubanpit]

What is your suggestion?

As far as I can tell, when running conan remote commands the output does not depend on the verbosity level.
I tried setting it from command line and conan remote -vquiet disable '*' is not considered a valid command, other variations just ignore the setting and print the same output.
I tried setting it from environment variable CONAN_LOG_LEVEL, but it is again ignored.
From a quick look at the code I would guess it is not implemented at the moment, I think it would be nice to have.

Have you read the CONTRIBUTING guide?

• I've read the CONTRIBUTING guide

[memsharded]

Hi @cubanpit

Thanks for your suggestion.

I tried setting it from command line and conan remote -vquiet disable '*' is not considered a valid command, other variations just ignore the setting and print the same output.

I'd like to understand what would be the problem we would be trying to address here. Yes, it is true that at the moment the remote commands doesn't implement different levels of verbosity, but this is because their output is always very reduced, so what would be the benefit of conan remote disable not reporting what remotes were actually disabled?

[cubanpit]

I would expect consistency with what the verbose options are saying, for example -werror would only print errors, the listing of the disabled remotes is not an error.
Of course this is only a minor detail, but it is nice to be able to set a policy and know that all Conan commands are respecting it.

[memsharded]

Sure, sure, I agree that things should be consistent, I was trying to understand the "magnitude" of the issue and trying to learn if there was there some other use case, flow, or anything that we could be missing, that would be affected by this, also to be able to prioritize the work.