Files.app: Remove navigationVolumeMap from the background page.

Previously Files.app uses navigationVolumeMap which is a map from devicePath to
volumeId. When the notification saying "Open removable device" is clicked,
Files.app finding corresponding volumeId from the map, and navigate to the
volume.

Files.app: Remove navigationVolumeMap from the background page.

But if the background page once closed, the map is cleared and the app cannot
find the corresponding volume.

The CL adds devicePath field to VolumeInfo, and let the app find the
corresponding volume information directly without using the map.

BUG=419107
TEST=repro steps of the bug.

Committed: https://crrev.com/86a0c99d060868dddfa4abaa42b990e03ac284d3
Cr-Commit-Position: refs/heads/master@{#297792}

[hirono, 2014-10-01 13:36:52]

hirono@chromium.org changed reviewers:
+ yoshiki@chromium.org

[hirono, 2014-10-01 13:36:53]

Previously Files.app uses navigationVolumeMap which is a map from devicePath to
volumeId. When the notification saying "Open removable device" is clicked,
Files.app finding corresponding volumeId from the map, and navigate to the
volume.

But if the background page once closed, the map is cleared and the app cannot
find the corresponding volume.

The CL adds devicePath field to VolumeInfo, and let the app find the
corresponding volume information directly without using the map.

[hirono, 2014-10-01 13:37:47]

PTAL the CL? Thank you!

[yoshiki, 2014-10-02 04:40:39]

lgtm

[hirono, 2014-10-02 07:38:24]

The CQ bit was checked by hirono@chromium.org

[hirono, 2014-10-02 07:38:32]

On 2014/10/02 04:40:39, yoshiki wrote:
> lgtm

Thank you!

[hirono, 2014-10-02 07:38:34]

On 2014/10/02 04:40:39, yoshiki wrote:
> lgtm

Thank you!

[commit-bot: I haz the power, 2014-10-02 07:38:48]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/612303005/20001

[commit-bot: I haz the power, 2014-10-02 07:46:07]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-10-02 07:46:08]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[hirono, 2014-10-02 08:18:58]

The CQ bit was checked by hirono@chromium.org

[commit-bot: I haz the power, 2014-10-02 08:19:23]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/612303005/40001

[commit-bot: I haz the power, 2014-10-02 08:25:13]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-10-02 08:25:14]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
  linux_chromium_chromeos_rel_swarming on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[hirono, 2014-10-02 08:30:07]

The CQ bit was checked by hirono@chromium.org

[commit-bot: I haz the power, 2014-10-02 08:31:16]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/612303005/60001

[commit-bot: I haz the power, 2014-10-02 08:42:22]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-10-02 08:42:23]

Try jobs failed on following builders:
  linux_chromium_rel_swarming on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[hirono, 2014-10-02 08:55:21]

The CQ bit was checked by hirono@chromium.org

[commit-bot: I haz the power, 2014-10-02 08:55:38]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/612303005/80001

[commit-bot: I haz the power, 2014-10-02 09:52:46]

Committed patchset #5 (id:80001) as 55119da2a733534779e643780cb501218ced6188

[commit-bot: I haz the power, 2014-10-02 09:53:25]

Patchset 5 (id:??) landed as
https://crrev.com/86a0c99d060868dddfa4abaa42b990e03ac284d3
Cr-Commit-Position: refs/heads/master@{#297792}