Don't call initChromiumBrowserProcessForTests() in the linker tests

They do async initialization after that anyway, this does redundant
resource loading. The method will be going away shortly.

R=boliu@chromium.org

Bug: 961849
Change-Id: Iea16a3873bf060abd2a13333f3508fa2a0df0593
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1675342Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#672163}

content/shell/android/linker_test_apk/src/org/chromium/chromium_linker_test_apk/ChromiumLinkerTestActivity.java

@@ -94,9 +94,6 @@ public class ChromiumLinkerTestActivity extends Activity {
         // Now, start a new renderer process by creating a new view.
         // This will run the test runner in the renderer process.
 
-        BrowserStartupController.get(LibraryProcessType.PROCESS_BROWSER)
-                .initChromiumBrowserProcessForTests();
-
         LayoutInflater inflater =
                 (LayoutInflater) getSystemService(Context.LAYOUT_INFLATER_SERVICE);
         View view = inflater.inflate(R.layout.test_activity, null);