[iOS] Remove spurious DCHECK from BVC.

The DCHECK in the BVC's openNewTabFromOriginPoint: method doesn't
guard against anything, and is documented as being possible to hit
in ordinary usage, so it doesn't seem to be a correctness assertion.

As far as I can tell the conditional around the screenshot after the
DCHECK will catch any other issues that could arise in this method.

Fixed: 1488872
Change-Id: I040bc7f4e0bb8f2746fc059787e139f3c709e635
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4941970
Commit-Queue: Mark Cogan <marq@chromium.org>
Reviewed-by: Federica Germinario <fedegermi@google.com>
Cr-Commit-Position: refs/heads/main@{#1210139}

ios/chrome/browser/ui/browser_view/browser_view_controller.mm

@@ -639,11 +639,6 @@ - (void)openNewTabFromOriginPoint:(CGPoint)originPoint
   };
 
   [self setLastTapPointFromCommand:originPoint];
-  // The new tab can be opened before BVC has been made visible onscreen.  Test
-  // for this case by checking if the parent container VC is currently in the
-  // process of being presented.
-  DCHECK(self.visible || self.dismissingModal ||
-         self.parentViewController.isBeingPresented);
 
   // In most cases, we want to take a snapshot of the current tab before opening
   // a new tab. However, if the current tab is not fully visible (did not finish