[net] Remove downloads bug triage from //net triage responsibilities.

net/docs/bug-triage-labels.md

 # Chrome Network Bug Triage : Components and labels
 
 ## Some network component caveats
 
-* **UI>Browser>Downloads**
-
-    Despite the name, this covers all issues related to downloading a file
-    except saving entire pages (which is **Blink>SavePage**), not just UI
-    issues.  Most downloads bugs will have the word "download" or "save as" in
-    the description.  Issues with the HTTP server for the Chrome binaries are
-    not downloads bugs.
-
-* **UI>Browser>SafeBrowsing**
-
-    Bugs that have to do with the process by which a URL or file is determined
-    to be dangerous based on our databases, or the resulting interstitials.
-    Determination of danger based purely on content-type or file extension
-    belongs in **UI>Browser>Downloads**, not SafeBrowsing.
-
 * **Internals>Network>SSL**
 
     This includes issues that should be also tagged as **Security>UX**
     (certificate error pages or other security interstitials, omnibox indicators
     that a page is secure), and more general SSL issues.  If you see requests
     that die in the SSL negotiation phase, in particular, this is often the
     correct component.
 
 * **Internals>Network>DataProxy**
 
@@ skipping 30 matching lines @@
 
     Covers SDCH and gzip issues.  `ERR_CONTENT_DECODING_FAILED` indicates a
     problem at this layer, and bugs here can also cause response body
     corruption.
 
 ## Common non-network components
 
 Bugs in these areas often receive the **Internals>Network** component, though
 they fall largely outside the purview of the network stack team:
 
+* **UI>Browser>Downloads**
+
+    Despite the name, this covers all issues related to downloading a file
+    except saving entire pages (which is **Blink>SavePage**), not just UI
+    issues.  Most downloads bugs will have the word "download" or "save as" in
+    the description.  Issues with the HTTP server for the Chrome binaries are
+    not downloads bugs.
+
+* **UI>Browser>SafeBrowsing**
+
+    Bugs that have to do with the process by which a URL or file is determined
+    to be dangerous based on our databases, or the resulting interstitials.
+    Determination of danger based purely on content-type or file extension
+    belongs in **UI>Browser>Downloads**, not SafeBrowsing.
+
 * **Blink>Forms**
 
     Issues submitting forms, forms having weird data, forms sending the wrong
     method, etc.
 
 * **Blink>Loader**
 
     Cross origin issues are sometimes loader related.  Blink also has an
     in-memory cache, and when it's used, requests don't appear in
     about:net-internals.  Requests for the same URL are also often merged there
@@ skipping 84 matching lines @@
     beyond the lifetime of incognito tabs, etc).  Generally used in conjunction
     with other components.
 
 ## Common labels
 
 * **Type-Bug-Security**
 
     Security related bug (Allows for code execution from remote site, allows
     crossing security boundaries, unchecked array bounds, etc) should be tagged
     with this label.