The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/5ddbfd5bc25825eb1017e08a68d8d75cf32908e9

commit 5ddbfd5bc25825eb1017e08a68d8d75cf32908e9
Author: Xiaochu Liu <xiaochu@chromium.org>
Date: Wed Dec 06 05:50:15 2017

Install cros components to own path naming space

To avoid path conflicts, we install chrome os components (only) to
dedicated path naming space (cros_components/[component name]).

Since the components currently used are small (printer drivers), the
cost to migrate it small. It's a good idea to migrate now.

BUG= chromium:789726 
TEST=update (ignore old locations)/install printer driver component on device.

Change-Id: I3276f73eaab50ec562d247d06eedb5c96ba183bf
Reviewed-on: https://chromium-review.googlesource.com/798225
Commit-Queue: Xiaochu Liu <xiaochu@chromium.org>
Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Cr-Commit-Position: refs/heads/master@{#522020}
[modify] https://crrev.com/5ddbfd5bc25825eb1017e08a68d8d75cf32908e9/chrome/browser/component_updater/cros_component_installer.cc
[modify] https://crrev.com/5ddbfd5bc25825eb1017e08a68d8d75cf32908e9/components/component_updater/component_installer.cc