"kpm restore --quiet" hides HTTP requests/cache information

[ChengTian]

parent #577

An interesting usage mentioned by @davidfowl is kpm --verbose restore --quiet. For my implementation, in this case, --verbose wins and here is the reason:
If --quiet wins, kpm restore blocks without showing HTTP requests/cache information. So the user might not notice that he mistakenly specified --verbose and --quiet together because he might think that kpm restore is blocking for some silent operations.
If --verbose wins, we show a bunch of HTTP request/cache information instantly after the user hit Enter key. So the user can easily notice he specified --verbose. The basic idea is that we make the behavior obvious & quick enough to draw users' attention.

@Eilon , do you like the idea above? Or we can give an error saying --verbose and --quiet are mutually exclusive.

[ChengTian]

Some background knowledge:

1. kpm --verbose restore shows all information
2. kpm restore hides Attempting to resolve "{0}" and dependency graph
3. kpm restore --quiet hides Attempting to resolve "{0}", dependency graph and HTTP request/cache information

[Eilon]

I recommend making the description a bit more generic (we might eventually have more information beyond HTTP stuff).

E.g.:
Do not show output such as HTTP request/cache information

[Eilon]

The logic makes sense to me (verbose vs. quiet) so I'm fine with this.

[ChengTian]

Changed based on @Eilon 's feedbacks. Now the Reports class has 3 properties: Information, Verbose and Quiet. If you want the WriteLine() operation to be affected by --verbose, pass in Verbose. If you want the WriteLine() operation to be affected by --quiet, pass in Quiet. The values of Verbose and Quiet are determined ahead of time, so there is no decision making logic in later methods.

[davidfowl]

/cc @pranavkm Lets change our build scripts to use this.

[Eilon]

Sorry for the delay - looks much nicer!