diagnose_bloat.py: swap --silent with --verbose.

tools/binary_size/README.md

 # Tools for Analyzing Chrome's Binary Size
 
 These currently focus on Android and Linux platforms. However, some great tools
 for Windows exist and are documented here:
 
 https://www.chromium.org/developers/windows-binary-sizes
 
 There is also a dedicated mailing-list for binary size discussions:
 
 https://groups.google.com/a/chromium.org/forum/#!forum/binary-size
@@ skipping 11 matching lines @@
 
   * Default is to build just two revisions (before & after commit)
   * Rather than building, can fetch build artifacts from perf bots (`--cloud`)
 
 1. Measures all outputs using `resource_size.py` and `supersize`.
 1. Saves & displays a breakdown of the difference in binary sizes.
 
 ### Example Usage
 
     # Build and diff HEAD^ and HEAD.
-    tools/binary_size/diagnose_bloat.py HEAD
+    tools/binary_size/diagnose_bloat.py HEAD -v
 
     # Diff OTHERREV and REV using downloaded build artifacts.
-    tools/binary_size/diagnose_bloat.py REV --reference-rev OTHERREV --cloud
+    tools/binary_size/diagnose_bloat.py REV --reference-rev OTHERREV --cloud -v
 
     # Build and diff all contiguous revs in range OTHERREV..REV for src/v8.
-    tools/binary_size/diagnose_bloat.py REV --reference-rev OTHERREV --subrepo v8 --all
+    tools/binary_size/diagnose_bloat.py REV --reference-rev OTHERREV --subrepo v8 --all -v
 
     # Display detailed usage info (there are many options).
     tools/binary_size/diagnose_bloat.py -h
 
 ## Super Size
 
 Collect, archive, and analyze Chrome's binary size.
 Supports Android and Linux (although Linux
 [has issues](https://bugs.chromium.org/p/chromium/issues/detail?id=717550)).
 
@@ skipping 56 matching lines @@
 
 1. Diffing
 
   * Some heuristics for matching up before/after symbols.
 
 ### Usage: `archive`
 
 Collect size information and dump it into a `.size` file.
 
 *** note
-**Note:** Refer to 
+**Note:** Refer to
 [diagnose_bloat.py](https://cs.chromium.org/search/?q=file:diagnose_bloat.py+gn_args)
 for list of GN args to build a Release binary.
 ***
 
 Example:
 
     ninja -C out/Release -j 1000 apks/ChromePublic.apk
     tools/binary_size/supersize archive chrome.size --apk-file out/Release/apks/ChromePublic.apk -v
 
     # Linux:
@@ skipping 57 matching lines @@
 
   * Able to render size diffs (tint negative size red).
   * Break down by other groupings (Create from result of `SplitByName()`)
   * Render as simple tree view rather than 2d boxes
 
 1. Integrate with `resource_sizes.py` so that it tracks size of major
    components separately: chrome vs blink vs skia vs v8.
 1. Add dependency graph info, perhaps just on a per-file basis.
 
   * No idea how to do this, but Windows can do it via `tools\win\linker_verbose_tracking.py`