Use per-profile SafeBrowsing network context in ChromeBrowsingDataRemoverDelegate

This CL changes the ChromeBrowsingDataRemoverDelegate to use a per-
profile network context when clearing the Safe Browsing cookie, since
that cookie will be profile-scoped, going forward.

Bug: 1049833
Change-Id: Ifa09b8b89dc36efa37705223369f3fac162977d0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2357425Reviewed-by: Martin Šrámek <msramek@chromium.org>
Commit-Queue: Daniel Rubery <drubery@chromium.org>
Cr-Commit-Position: refs/heads/master@{#798694}

chrome/browser/browsing_data/chrome_browsing_data_remover_delegate.cc

@@ -710,7 +710,7 @@ void ChromeBrowsingDataRemoverDelegate::RemoveEmbedderData(
           g_browser_process->safe_browsing_service();
       if (sb_service) {
         mojo::Remote<network::mojom::CookieManager> cookie_manager;
-        sb_service->GetNetworkContext()->GetCookieManager(
+        sb_service->GetNetworkContext(profile_)->GetCookieManager(
             cookie_manager.BindNewPipeAndPassReceiver());
 
         network::mojom::CookieManager* manager_ptr = cookie_manager.get();