Interacting w/ virtual keyboard shouldn't dismiss Assistant.

Previously only workspace occluded bounds were checked. This handled
the default virtual keyboard case but not the floating virtual
keyboard case. To handle both cases, we need to check visual bounds.

Bug: b:140987575
Change-Id: I6d2012c28f1202181d5db27ab5dbea6b2f51952b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1836665
Commit-Queue: David Black <dmblack@google.com>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#702544}

ash/assistant/assistant_ui_controller.cc

@@ -694,8 +694,10 @@ void AssistantUiController::OnEvent(const ui::Event& event) {
 
   const gfx::Rect screen_bounds =
       container_view_->GetWidget()->GetWindowBoundsInScreen();
-  const gfx::Rect keyboard_bounds = keyboard::KeyboardUIController::Get()
-                                        ->GetWorkspaceOccludedBoundsInScreen();
+  const gfx::Rect keyboard_bounds =
+      keyboard::KeyboardUIController::Get()->IsKeyboardVisible()
+          ? keyboard::KeyboardUIController::Get()->GetVisualBoundsInScreen()
+          : gfx::Rect();
 
   // Pressed events outside our widget bounds should result in hiding of the
   // Assistant UI. The exception to this rule is if the user is interacting