Start transition the metrics library to non-static API. Use gmock in tests.

src/platform/metrics/README

 Copyright (c) 2010 The Chromium OS Authors. All rights reserved.
 Use of this source code is governed by a BSD-style license that can be
 found in the LICENSE file.
 
 The Chrome OS "metrics" package contains utilities for client-side
 user metric collection. The collected data is sent to Chrome for
 transport to the UMA server.
 
 
 ================================================================================
@@ skipping 14 matching lines @@
   to the module's link command). Both libmetrics.so and libmetrics.a
   are built and installed under $SYSROOT/usr/lib/. Note that by
   default -lmetrics will link against libmetrics.so, which is
   preferred.
 
 - To access the metrics library API in the module, include the
   <metrics_library.h> header file. The file is installed in
   $SYSROOT/usr/include/ when the metrics library is built and
   installed.
 
-- Currently, the API includes two static methods:
+- The API includes two methods:
+
+  bool MetricsLibrary::SendToUMA(const std::string& name, int sample,
+                                 int min, int max, int nbuckets)
+  sends a sample for a regular (exponential) histogram.
+
+  bool MetricsLibrary::SendEnumToUMA(const std::string& name, int sample,
+                                     int max)
+  sends a sample for an enumeration (linear) histogram.
+
+  Currently, the API also includes two deprecated static methods:
 
   bool MetricsLibrary::SendToChrome(const std::string& name, int sample,
                                     int min, int max, int nbuckets)
-  sends a sample for a regular (exponential) histogram.
-
   bool MetricsLibrary::SendEnumToChrome(const std::string& name, int sample,
                                         int max)
-  sends a sample for an enumeration (linear) histogram.
 
-  See API documentation in metrics_library.h under
+  See the API documentation in metrics_library.h under
   src/platform/metrics/.
 
-  TODO: It might be better to convert the API to a dynamic object.
-
 - On the target platform, shortly after the sample is sent it should
   be visible in Chrome through "about:histograms".
 
 
 ================================================================================
 Histogram Naming Convention
 ================================================================================
 
 Use TrackerArea.MetricName. For example:
 
@@ skipping 46 matching lines @@
 screen saver states to determine if the user is actively using the
 device or not and generates the corresponding data. The metrics daemon
 uses libmetrics to send the data to Chrome.
 
 The recommended way to generate metrics data from a module is to link
 and use libmetrics directly. However, the module could instead send
 signals to or communicate in some alternative way with the metrics
 daemon. Then the metrics daemon needs to monitor for the relevant
 events and take appropriate action -- for example, aggregate data and
 send the histogram samples.