lacros: Switch to using dogfood over fishfood.

We have now qualified our first dogfood release, so it's safe to enable
dogfood releases by default.

Bug: 1164154
Change-Id: I248bb8f5d2ea6dce1e2754a959b421cb1704d879
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2618365
Commit-Queue: Erik Chen <erikchen@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#841668}

chrome/browser/chromeos/crosapi/browser_loader.cc

@@ -33,7 +33,7 @@ namespace {
 // At that point, this feature can only be removed from the code and we can
 // switch unconditionally to the dogfood deployment..
 const base::Feature kLacrosPreferDogfoodOverFishfood{
-    "LacrosPreferDogfoodOverFishfood", base::FEATURE_DISABLED_BY_DEFAULT};
+    "LacrosPreferDogfoodOverFishfood", base::FEATURE_ENABLED_BY_DEFAULT};
 
 // Emergency kill switch in case the notification code doesn't work properly.
 const base::Feature kLacrosShowUpdateNotifications{

chrome/browser/chromeos/crosapi/browser_loader_unittest.cc

@@ -78,7 +78,7 @@ TEST_F(BrowserLoaderTest, ShowUpdateNotification) {
   EXPECT_EQ(0, delegate->set_lacros_update_available_);
 
   // Update check does not trigger an update notification.
-  constexpr char kLacrosFishfoodId[] = "hkifppleldbgkdlijbdfkdpedggaopda";
+  constexpr char kLacrosFishfoodId[] = "ldobopbhiamakmncndpkeelenhdmgfhk";
   browser_loader.OnEvent(
       UpdateClient::Observer::Events::COMPONENT_CHECKING_FOR_UPDATES,
       kLacrosFishfoodId);