Capture system logs from CrOS devices for standard gtest tests.

We capture the logs in system integration Tast tests, but not small
gtest tests. But it appears some gtests do need system logs, so this
pulls them for every gtest as well.

Also update old uses of the arg name.

Bug: None
Change-Id: I47de8617575dfda5a74d9d1319f3d9dbaad4714b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424817Reviewed-by: Dirk Pranke <dpranke@google.com>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809930}

testing/buildbot/gn_isolate_map.pyl

@@ -417,7 +417,7 @@
     "label": "//chromeos:chrome_all_tast_tests",
     "type": "generated_script",
     "args": [
-      "--vm-logs-dir=${ISOLATED_OUTDIR}",
+      "--logs-dir=${ISOLATED_OUTDIR}",
     ],
   },
   "chrome_app_unittests": {
@@ -750,7 +750,7 @@
     "label": "//chromeos:cros_browser_sanity_test",
     "type": "generated_script",
     "args": [
-      "--vm-logs-dir=${ISOLATED_OUTDIR}",
+      "--logs-dir=${ISOLATED_OUTDIR}",
       "cros_browser_sanity_test",
     ],
   },
@@ -794,7 +794,7 @@
     "label": "//chromeos:disk_usage_tast_test",
     "type": "generated_script",
     "args": [
-      "--vm-logs-dir=${ISOLATED_OUTDIR}",
+      "--logs-dir=${ISOLATED_OUTDIR}",
     ],
   },
   "display_unittests": {

tools/mb/mb.py

@@ -1467,6 +1467,7 @@ class MetaBuildWrapper(object):
           '../../testing/test_env.py',
           os.path.join('bin', 'run_%s' % target),
           '--flash',
+          '--logs-dir=${ISOLATED_OUTDIR}',
       ]
     elif use_xvfb and test_type == 'windowed_test_launcher':
       extra_files.append('../../testing/xvfb.py')