diagnose_apk_bloat.py: handle more rev options.

tools/binary_size/README.md

 # Tools for analyzing Chrome's binary size
 
 # Super Size
 
 Collect, archive, and analyze Chrome's binary size.
 
 ## "archive"
 
 Collect size information and dump it into a `.size` file. Mainly consists of
 symbol information parsed from a linker .map file.
@@ skipping 46 matching lines @@
 ### Example Usage:
 
     tools/binary_size/supersize diff before.size after.size --all
 
 # diagnose_apk_bloat.py
 
 Determine the cause of binary size bloat for a patch.
 
 ## Example Usage:
 
-    # Sync, build, and diff for HEAD and HEAD^.
-    tools/binary_size/diagnose_apk_bloat.py
+    # Build and diff HEAD^ and HEAD.
+    tools/binary_size/diagnose_apk_bloat.py HEAD
 
-    # Diff using downloaded build artifacts.
-    tools/binary_size/diagnose_apk_bloat.py --cloud --rev-with-patch REV
+    # Diff OTHERREV and REV using downloaded build artifacts.
+    tools/binary_size/diagnose_apk_bloat.py REV --reference-rev OTHERREV --cloud
+
+    # Build and diff contiguous revs in range OTHERREV..REV for src/v8.
+    tools/binary_size/diagnose_apk_bloat.py REV --reference-rev OTHERREV --subrepo v8 --all
 
     # Display detailed usage info (there are many options).
     tools/binary_size/diagnose_apk_bloat.py -h
 
 # Roadmap for Super Size:
 
 Tracked in https://crbug.com/681694
 
 1. More `archive` features:
 
@@ skipping 19 matching lines @@
 
 1. Integrate with `resource_sizes.py` so that it tracks size of major
    components separately: chrome vs blink vs skia vs v8.
 1. Speed up some steps (like normalizing names) via multiprocessing.
 1. Add dependency graph info, perhaps just on a per-file basis.
 
 # Roadmap for diagnose_apk_bloat.py:
 1. More `diagnose_apk_bloat.py` features:
 
   * Add more diff types (pak files, Java symbols, native symbols).
-  * Support performing diffs on all revs in a given range.
   * Support local builds for revs before supersize existed.