Tweak apk_size_regressions.md to be more explicit about a couple things

tools/perf/docs/apk_size_regressions.md

 # How to Deal with Android Size Alerts
 
-*Most alerts should not have a bug created for them. Please read on...*
+*Not all alerts should not have a bug created for them. Please read on...*
 
 ### If the alert is for "other lib size" or "Unknown files size":
  * File a bug against agrieve@ to fix
    [resource_sizes.py](https://cs.chromium.org/chromium/src/build/android/resource_sizes.py).
  * ...or fix it yourself. This script will output the list of unknown
    filenames.
 
 ### If the alert is a downstream size alert (aka, for Monochrome.apk):
  * The regression most likely already occurred in the upstream
    MonochromePublic.apk target. Look at the
    [upstream graphs](https://chromeperf.appspot.com/report?sid=cfc29eed1238fd38fb5e6cf83bdba6c619be621b606e03e5dfc2e99db14c418b&num_points=1500)
    to find the culprit & de-dupe with upstream alerts.
  * If no upstream regression was found, look through the downstream commits
    within the given date range to find the culprit.
     * Via `git log --format=fuller` (be sure to look at `CommitDate` and not
       `AuthorDate`)
 
-### If the alert is for a roll:
+### If the alert is for a roll, or has multiple commits listed:
  * Use a bisect to try and determine a more precise commit.
     * Except don't. Bisects for these alerts [are currently broken](https://bugs.chromium.org/p/chromium/issues/detail?id=678338).
+    * Until this is fixed, just file a bug and assign to agrieve@.
 
 ### What to do once the commit is identified:
  * If the code seems to justify the size increase:
     1. Annotate the code review with the following (replacing **bold** parts):
        > FYI - this added **20kb** to Chrome on Android. No action is required
        > (unless you can think of an obvious way to reduce the overhead).
        >
        > Link to size graph:
 [https://chromeperf.appspot.com/report?sid=cfc29eed1238fd38fb5e6cf83bdba6c619be621b606e03e5dfc2e99db14c418b&rev=**440074**](https://chromeperf.appspot.com/report?sid=cfc29eed1238fd38fb5e6cf83bdba6c619be621b606e03e5dfc2e99db14c418b&rev=440074)
     2. Add an entry to
       [this spreadsheet](https://docs.google.com/spreadsheets/d/1GrRkszV7Oy5pVsaMb5Eb6s8izW9t4dElBxIH3iGq93o/edit#gid=1894856744)
       to document the increase (also Update the "Themes / Thoughts" tab if
       applicable).
  * If the code might not justify the size increase:
     1. File a bug and assign to the author to follow-up (and link them to
        [Debugging Apk Size Increase](https://chromium.googlesource.com/chromium/src/+/master/tools/perf/docs/apk_size_regressions.md#Debugging-Apk-Size-Increase)).
+        * Change the bug's title from X% to XXkb
+        * Paste in link to commit that is at fault.
+        * Remove label: `Restrict-View-Google`
+        * Add label: `apk-size`
+        * TODO(agrieve): [https://github.com/catapult-project/catapult/issues/3150](Change bug template to match these instructions)
     2. Add an entry to
       [this spreadsheet](https://docs.google.com/spreadsheets/d/1GrRkszV7Oy5pVsaMb5Eb6s8izW9t4dElBxIH3iGq93o/edit#gid=1894856744)
       to document the increase.
 
 # Debugging Apk Size Increase
 
 ## Step 1: Identify where the extra bytes came from
 
 Figure out which file within the .apk increased by looking at the size graphs
 showing the breakdowns.
@@ skipping 30 matching lines @@
         * This currently just shows a list of symbols added / removed rather than
           taking into account method body sizes.
         * Enhancements to this tool tracked at
           [crbug/678044](https://bugs.chromium.org/p/chromium/issues/detail?id=678044).
  * If the growth is from images, ensure they are optimized:
     * Would it be smaller as a VectorDrawable?
     * If it's lossy, consider using webp.
     * Ensure you've optimized with
       [tools/resources/optimize-png-files.sh](https://cs.chromium.org/chromium/src/tools/resources/optimize-png-files.sh).
     * There is some [Googler-specific guidance](https://goto.google.com/clank/engineering/best-practices/adding-image-assets) as well.