Make service tab launcher a component

chrome/android/shell/java/AndroidManifest.xml.jinja2

 <?xml version="1.0" encoding="utf-8"?>
 
 <!-- Copyright 2014 The Chromium Authors. All rights reserved.
 
      Use of this source code is governed by a BSD-style license that can be
      found in the LICENSE file.
  -->
 
 <manifest xmlns:android="http://schemas.android.com/apk/res/android"
     package="org.chromium.chrome.shell">
@@ skipping 171 matching lines @@
 
         <!-- Broadcast receiver that will be notified of account changes. -->
         <receiver android:name="org.chromium.chrome.shell.signin.AccountsChangedReceiver">
             <intent-filter>
                 <action android:name="android.accounts.LOGIN_ACCOUNTS_CHANGED" />
             </intent-filter>
         </receiver>
 
         <meta-data android:name="org.chromium.content.browser.SMART_CLIP_PROVIDER"
                    android:value="org.chromium.content.browser.SmartClipProvider" />
-        <meta-data android:name="org.chromium.chrome.browser.SERVICE_TAB_LAUNCHER"
+        <meta-data android:name="org.chromium.components.service_tab_launcher.SERVICE_TAB_LAUNCHER"
                    android:value="org.chromium.chrome.shell.ChromeShellServiceTabLauncher" />
 
         <!-- Precache service. -->
         <service android:name="org.chromium.chrome.browser.precache.PrecacheService"
             android:exported="false" />
         <receiver android:name="org.chromium.chrome.browser.precache.PrecacheServiceLauncher">
             <intent-filter>
                 <action android:name="android.intent.action.ACTION_POWER_CONNECTED"/>
                 <action android:name="android.intent.action.ACTION_POWER_DISCONNECTED"/>
                 <action android:name="android.net.conn.CONNECTIVITY_CHANGE" />
@@ skipping 18 matching lines @@
         <!-- Media route controllers to use for remote playback (cast).
              This is here, rather than in code, since it varies between upstream and downstream,
              yet we need this list of classes in the notification service, which belongs upstream
              and doesn't run the downstream Clank startup code. The Cast code will, for each media element,
              choose the first MediaRouteController that can play it, so the order of the list can be important.
              The most specific MediaRouteControllers should be listed first, followed by more generic ones -->
         <meta-data android:name="org.chromium.content.browser.REMOTE_MEDIA_PLAYERS"
             android:value="org.chromium.chrome.browser.media.remote.DefaultMediaRouteController"/>
     </application>
 </manifest>