Make FeatureList override state be plumbed to renderer processes.

Previously, the browser copied over verbatim the --enable-features
and --disable-features command-line. However, this wouldn't have
captured overrides as a result of field trials. This change updates
the logic to include those in the list. The new logic will continue
to work for plumbing command-lines as well, since those are also
registered using the override mechanism.

Note: There's still some follow-up work that needs to be done to
plumb the FieldTrial association state (so that a FieldTrial that's
not active will get activated in the renderer if the associated
Feature is queried). But this can be supported in a follow-up CL
that builds on top of this one.

BUG=561077

Review URL: https://codereview.chromium.org/1471693007

Cr-Commit-Position: refs/heads/master@{#362294}


CrOS-Libchrome-Original-Commit: 86340191dcd4ad3ab7e6e4c7500ff9a5a8e9c3b0
3 files changed
tree: 29ce3361aaa386bf733a92da38a402206328d221
  1. base/
  2. build/
  3. components/
  4. dbus/
  5. device/
  6. ipc/
  7. mojo/
  8. testing/
  9. third_party/
  10. ui/