Fixed inaccurate selector causing DOM focus instability.

A previous migration to using cr-link-row instead of directly using
a subpage-arrow class cr-icon-button did not update the selector in
forcusConfig_ to match. As a result, when the user routes back to the
OS search page, the DOM and a11y focus go to the full page.

This CL updates the selector in focusConfig_.

Bug: 1003992
Change-Id: I57bf325a9ea5fe4f7719924cf9c2abbedde9de9e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1897492
Commit-Queue: Jordy Greenblatt <jordynass@chromium.org>
Commit-Queue: Hector Carmona <hcarmona@chromium.org>
Reviewed-by: Hector Carmona <hcarmona@chromium.org>
Reviewed-by: Jordy Greenblatt <jordynass@chromium.org>
Auto-Submit: Jordy Greenblatt <jordynass@chromium.org>
Cr-Commit-Position: refs/heads/master@{#712351}

chrome/browser/resources/settings/chromeos/os_search_page/os_search_page.js

@@ -59,8 +59,7 @@ Polymer({
     this.focusConfig_ = new Map();
     if (settings.routes.GOOGLE_ASSISTANT) {
       this.focusConfig_.set(
-          settings.routes.GOOGLE_ASSISTANT.path,
-          '#assistantSubpageTrigger .subpage-arrow');
+          settings.routes.GOOGLE_ASSISTANT.path, '#assistantSubpageTrigger');
     }
   },
 

chrome/browser/resources/settings/search_page/search_page.js

@@ -68,8 +68,7 @@ Polymer({
     // <if expr="chromeos">
     if (settings.routes.GOOGLE_ASSISTANT) {
       this.focusConfig_.set(
-          settings.routes.GOOGLE_ASSISTANT.path,
-          '#assistantSubpageTrigger .subpage-arrow');
+          settings.routes.GOOGLE_ASSISTANT.path, '#assistantSubpageTrigger');
     }
     // </if>
   },