Remove shaped desktop support from remoting host and client.

remoting/proto/video.proto

Index: remoting/proto/video.proto
diff --git a/remoting/proto/video.proto b/remoting/proto/video.proto
index 66e7ce204a9be435056a0752a41998473a0c267f..252287309968d4f35ae682b16cb450f1999da1c3 100644
--- a/remoting/proto/video.proto
+++ b/remoting/proto/video.proto
@@ -58,14 +58,6 @@ message VideoPacket {
   // starting to capture this video frame.
   optional int64 latest_event_timestamp = 9;
 
-  // Provides the new shape for this frame, iff |use_desktop_shape| is true.
-  repeated Rect desktop_shape_rects = 10;

[joedow, 2016/03/25 01:26:18]

Is it useful to leave a comment that fields 10 and 11 were retired so they
aren't accidentally reused in the future?

[Jamie, 2016/03/25 17:17:18]

Or even rename them DEPRECATED_* so that they can't be reused?

[Sergey Ulanov, 2016/03/25 19:33:14]

Done.

[Sergey Ulanov, 2016/03/25 19:33:14]

If we keep them as deprecated protobuf will still generate the code for these
fields. In the past we were removing fields and I think it's very unlikely to
cause any problems. It's usually obvious which fields have been used when there
are gaps in the field IDs. Normally these fields IDs would be marked as
reserved, see
https://developers.google.com/protocol-buffers/docs/reference/proto2-spec#res...
. But this feature is not supported in the version of protobuf we use.

-
-  // True when |desktop_shape_rects| should be used, false to indicate that
-  // the frame is un-shaped. If the shape has not changed since the preceding
-  // frame then this field should be omitted.
-  optional bool use_desktop_shape = 11;
-
   // Optional frame timestamp. Used in tests to estimate frame latency.
   optional int64 timestamp = 12;