Add UMA metrics for Chrome OS Bluetooth system daemon

This adds the following histograms and their definitions.

[Histograms]
- BlueZ.AdapterLost
- BlueZ.NumberOfExistingAdvertisements

BUG=chromium:724720
[email protected]

(cherry picked from commit b5a0727)

Change-Id: I44e8cb0df131efff57582d5bbbda7abe2b16a97b
Reviewed-on: https://chromium-review.googlesource.com/722076
Commit-Queue: Miao-chen Chou <[email protected]>
Reviewed-by: Rahul Chaturvedi <[email protected]>
Reviewed-by: Robert Kaplow <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#509544}
Reviewed-on: https://chromium-review.googlesource.com/728349
Reviewed-by: Miao-chen Chou <[email protected]>
Cr-Commit-Position: refs/branch-heads/3239@{#73}
Cr-Branched-From: adb61db-refs/heads/master@{#508578}

tools/metrics/histograms/histograms.xml

@@ -7408,6 +7408,25 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
   </summary>
 </histogram>
 
+<histogram name="BlueZ.AdapterLost" units="losses">
+  <owner>[email protected]</owner>
+  <summary>
+    This is specific to Chrome OS. Records an occurance of a Bluetooth adapter
+    being lost. This helps us better understand the Bluetooth controller drop
+    issue in the field.
+  </summary>
+</histogram>
+
+<histogram name="BlueZ.NumberOfExistingAdvertisements" units="advertisements">
+  <owner>[email protected]</owner>
+  <summary>
+    This is specific to Chrome OS. Records the number of existing advertisements
+    when registering for a new advertisement. This helps us better understand
+    the common amount of advertisments used and the registration failures due to
+    the limited number of advertisement slots.
+  </summary>
+</histogram>
+
 <histogram name="BlueZ.ReasonOfDisconnection" enum="BlueZReasonOfDisconnection">
   <owner>[email protected]</owner>
   <summary>