chromeos: scheduler-configuration flag never expires.

Bug: 1025993
Change-Id: I780717cffbdd5d18f030667e52874d58d21439b8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2572785
Commit-Queue: Avi Drissman <avi@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Auto-Submit: Greg Kerr <kerrnel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#834593}

chrome/browser/flag-metadata.json

@@ -4267,7 +4267,11 @@
   {
     "name": "scheduler-configuration",
     "owners": [ "kerrnel", "mnissler" ],
-    "expiry_milestone": 88
+    // This flag never expires because some users need to override CPU security
+    // settings for performance gains, at their own risk. Chrome OS users cannot
+    // modify the command line, so a flag is the publicly documented mechanism
+    // exposed to users.
+    "expiry_milestone": -1
   },
   {"name": "schemeful-same-site",
     "owners": [ "bingler", "chlily" ],

chrome/browser/flag-never-expire-list.json

@@ -83,6 +83,7 @@
   "reader-mode-heuristics",
   "record-web-app-debug-info",
   "release-notes-notification-all-channels",
+  "scheduler-configuration",
   "set-market-url-for-testing",
   "show-autofill-type-predictions",
   "show-bluetooth-debug-log-toggle",