Fix the references to the ui.ChromeLogin

ui.ChromeLogin and ui.ChromeLoginGAIA were renamed in
http://crrev/c/2981353

Bug: b:187788829, 1227801, 1167243, 1115622
Change-Id: I31359f59ac35347aa75809d461a61ea383eb8512
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3018208
Commit-Queue: Roman Sorokin [CET] <rsorokin@chromium.org>
Commit-Queue: Dominic Battré <battre@chromium.org>
Auto-Submit: Roman Sorokin [CET] <rsorokin@chromium.org>
Reviewed-by: Dominic Battré <battre@chromium.org>
Cr-Commit-Position: refs/heads/master@{#900399}

chromeos/tast_control.gni

@@ -13,10 +13,10 @@ tast_disabled_tests_from_chrome_all = [
   "hwsec.ChapsRSAPSS",
 
   # crbug.com/1167243
-  "ui.ChromeLogin",
+  "login.Chrome",
 
   # crbug.com/1115622
-  "ui.ChromeLoginGAIA",
+  "login.ChromeGAIA",
 
   # crbug.com/1099695
   "platform.Drivefs",

docs/testing/chromeos_debugging_tips.md

@@ -103,7 +103,7 @@ To run a Tast test the same way it's ran on Chrome's builders:
 
 - Finally, run the Tast test on the device via the `cros_run_test` tool under
   `//third_party/chromite/bin/`. eg:
-  `cros_run_test --device $DEVICE_IP --tast ui.ChromeLogin`. See [here] for more
+  `cros_run_test --device $DEVICE_IP --tast login.Chrome`. See [here] for more
   info on cros_run_test.
 
 ## Telemetry