Remove assertion for duplicate profile creation

This assertion was triggering relatively frequently. Remove it and
replace with a condition to avoid re-binding the cookie observer.

Bug: 358111679
Change-Id: Ide06bbee0674784998f696f9f3e6993ccd7d4f75
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5771151
Auto-Submit: Brett Wilson <brettw@chromium.org>
Reviewed-by: Devlin Cronin <rdevlin.cronin@chromium.org>
Commit-Queue: Devlin Cronin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1338827}

chrome/browser/extensions/api/cookies/cookies_api.cc

diff --git a/chrome/browser/extensions/api/cookies/cookies_api.cc b/chrome/browser/extensions/api/cookies/cookies_api.cc
index 4079c99..6276072 100644
--- a/chrome/browser/extensions/api/cookies/cookies_api.cc
+++ b/chrome/browser/extensions/api/cookies/cookies_api.cc
@@ -175,13 +175,9 @@
   // When an off-the-record spinoff of |profile_| is created, start listening
   // for cookie changes there. The OTR receiver should never be bound, since
   // there wasn't previously an OTR profile.
-
-  // Note: this assumes OnOffTheRecordProfileCreated() would only be called for
-  // _primary_ OTR profiles (on platforms we care about). If that's not the
-  // case, we would change this to fail gracefully and check the presence of a
-  // primary OTR profile.
-  CHECK(!otr_receiver_.is_bound());
-  BindToCookieManager(&otr_receiver_, off_the_record);
+  if (!otr_receiver_.is_bound()) {
+    BindToCookieManager(&otr_receiver_, off_the_record);
+  }
 }
 
 void CookiesEventRouter::MaybeStartListening() {