Run lockScreen and loginStatus tests at the end

of defaultTests because lockScreen test changes the session state.

Bug: None
Test: No functionality change.
Change-Id: I3c6f6353525e97b6a547684066f26a30d8c9f3cf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1862718
Commit-Queue: Mitsuru Oshima <oshima@chromium.org>
Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Cr-Commit-Position: refs/heads/master@{#706283}

chrome/test/data/extensions/api_test/autotest_private/test.js

@@ -17,10 +17,6 @@ var defaultTests = [
     chrome.autotestPrivate.shutdown(true);
     chrome.test.succeed();
   },
-  function lockScreen() {
-    chrome.autotestPrivate.lockScreen();
-    chrome.test.succeed();
-  },
   function simulateAsanMemoryBug() {
     chrome.autotestPrivate.simulateAsanMemoryBug();
     chrome.test.succeed();
@@ -501,6 +497,14 @@ var defaultTests = [
     chrome.autotestPrivate.arcAppTracingStart(chrome.test.callbackFail(
         'Failed to start custom tracing.'));
   },
+
+  // KEEP |lockScreen()| TESTS AT THE BOTTOM OF THE defaultTests AS IT WILL
+  // CHANGE THE SESSION STATE TO LOCKED STATE.
+  function lockScreen() {
+    chrome.autotestPrivate.lockScreen();
+    chrome.test.succeed();
+  },
+  // ADD YOUR TEST BEFORE |lockScreen()| UNLESS YOU WANT TO RUN TEST IN LOCKED
 ];
 
 var arcEnabledTests = [