remoting: Import ChromotingEvent proto.

The new gRPC telemetry service uses the ChromotingEvent proto directly
rather than taking a dictionary of key-value pairs, so the proto needs
to be imported into Chromium.

Bug: 968348
Change-Id: I55e79fec24761fb1e3274a0e406cb3d93d10578f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636550
Commit-Queue: Erik Jensen <rkjnsn@chromium.org>
Reviewed-by: Joe Downing <joedow@chromium.org>
Reviewed-by: Yuwei Huang <yuweih@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664882}

remoting/proto/remoting/v1/BUILD.gn

@@ -66,11 +66,20 @@ cc_grpc_library("remote_support_host_grpc_library") {
   ]
 }
 
+proto_library("chromoting_event_proto") {
+  sources = [
+    "chromoting_event.proto",
+  ]
+}
+
 proto_library("telemetry_messages") {
   sources = [
     "generic_log_entry.proto",
     "telemetry_messages.proto",
   ]
+  deps = [
+    ":chromoting_event_proto",
+  ]
 }
 
 cc_grpc_library("telemetry_grpc_library") {

remoting/proto/remoting/v1/telemetry_messages.proto

@@ -8,12 +8,12 @@ option optimize_for = LITE_RUNTIME;
 
 package remoting.apis.v1;
 
+import "chromoting_event.proto";
 import "generic_log_entry.proto";
 
 // Contains one or more ChromotingEvents to use for generating telemetry events.
 message ChromotingEventData {
-  // TODO(yuweih): Uncomment and fix this:
-  // repeated chromoting_extensions.ChromotingEvent events = 1;
+  repeated ChromotingEvent events = 1;
 }
 
 // Contains a GenericLogEntry for generating a telemetry event.