Update documentation for pushing new FileTypePolicies

The script to push a new policy has moved to components, but we didn't
update the documentation.

Change-Id: I34bc6259c88db541056b098b587d7cfab9e0e8ad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2469460
Auto-Submit: Daniel Rubery <drubery@chromium.org>
Reviewed-by: Varun Khaneja <vakh@chromium.org>
Commit-Queue: Daniel Rubery <drubery@chromium.org>
Cr-Commit-Position: refs/heads/master@{#818008}

chrome/browser/resources/safe_browsing/README.md

@@ -16,7 +16,7 @@ Rendered version of this file: https://chromium.googlesource.com/chromium/src/+/
     * Wait 1-3 day for this to run on Canary to verify it doesn't crash Chrome.
     * In a synced checkout, run the following to generate protos for all
       platforms and push them to GCS. Replace the arg with your build directory:
-        * % `chrome/browser/resources/safe_browsing/push_file_type_proto.py -d
+        * % `components/safe_browsing/core/resources/push_file_type_proto.py -d
           out-gn/Debug`
     * It will ask you to double check its actions before proceeding.  It will
       fail if you're not a member of
@@ -42,7 +42,7 @@ versions on Canary/Dev channel). Rolling back a bad version is best achieved by:
   * **Upload** the new version of the file types.
     * In a synced checkout, run the following to generate protos for all
       platforms and push them to GCS. Replace the arg with your build directory:
-        * % `chrome/browser/resources/safe_browsing/push_file_type_proto.py -d
+        * % `components/safe_browsing/core/resources/push_file_type_proto.py -d
           out-gn/Debug`
   * Create a new cohort.
     * Under _Cohorts_, click _Manage_, then _Create Subcohort_ of Auto.