Add a new "Configure" mechanism to CLD browser-side data interfaces.

chrome/browser/component_updater/cld_component_installer.h

Index: chrome/browser/component_updater/cld_component_installer.h
diff --git a/chrome/browser/component_updater/cld_component_installer.h b/chrome/browser/component_updater/cld_component_installer.h
index b226aac872843253a850d655287cfbb1b50c14a5..ff4e84871b956d0376dab617d5809b762ab3dbcc 100644
--- a/chrome/browser/component_updater/cld_component_installer.h
+++ b/chrome/browser/component_updater/cld_component_installer.h
@@ -60,6 +60,10 @@ class CldComponentInstallerTraits : public ComponentInstallerTraits {
   // This method is threadsafe.
   static void SetLatestCldDataFile(const base::FilePath& path);
 
+  // Allows testing code to detect the file path that was ultimately set in

[Sorin Jianu, 2014/07/29 17:56:56]

Can this code be for production, in other words, why do we have to special case
it for test only? In there an issue with exposing an accessor for the latest
data file?

[Andrew Hayden (chromium.org), 2014/07/29 19:51:55]

There is no issue, but there is also no need. It's a one-way thing, you set it
and forget it. The only thing that would need this info is that code in
components/translate, which by definition should not have dependencies on THIS
code.

If we do have a need for it, I'm happy to remove the _ForTest suffix.

+  // SetLatestCldDataFile.
+  static base::FilePath GetLatestCldDataFile_ForTest();
+
   DISALLOW_COPY_AND_ASSIGN(CldComponentInstallerTraits);
 };