Avoid using `isolated` wrt. AssociatedInterfaces.

The term `isolated` is already widely used for origins. Using it also
to describe AssociatedInterfacePtrs and AssociatedInterfaceRequests
that are associated with dedicated or a disconnected message pipe 
(mostly for testing) is confusing. Instead, use the words `dedicated`
and `disconnected`, respectively.

Bug: 729021
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_site_isolation
Change-Id: Ie44893453fc0033f09eecac41af725f5123d07e4
Reviewed-on: https://chromium-review.googlesource.com/743011
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Yuzhu Shen <yzshen@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Balazs Engedy <engedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#513431}

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