Changes client_token to be client_auth_token.

blimp/common/proto/protocol_control.proto

Index: blimp/common/proto/protocol_control.proto
diff --git a/blimp/common/proto/protocol_control.proto b/blimp/common/proto/protocol_control.proto
index f2f705605a441e4b08821bdc5c0d8293ec85d149..765f731439ff3ff9f404906eb397568e580ab11a 100644
--- a/blimp/common/proto/protocol_control.proto
+++ b/blimp/common/proto/protocol_control.proto
@@ -15,7 +15,7 @@ message CheckpointAckMessage {
 
 // Contains Client->Engine information to establish an authenticated connection.
 message StartConnectionMessage {
-  optional string client_token = 1;
+  optional string client_auth_token = 1;

[maniscalco, 2016/08/30 18:05:09]

I'm not so sure I'd change this proto field name since the value needs to match
the "client_token" returned by the assigner, but I don't feel that strongly at
this point.  Wez, WDYT?

[Wez, 2016/09/01 02:29:26]

My preference would be to rename it here, for consistency with the rest of the
Chromium-side code - then from the Chromium side only the Assigner API field has
the client_token name. Make sense?

[maniscalco, 2016/09/01 14:44:30]

I'm fine with renaming it as well, but just so we're clear things still won't be
fully consistent throughout chromium as there are other chromium places that
refer to it as "client token" that aren't being changed (e.g. the command line
flags).  And, IMO, it's not worth changing those.

[CJ, 2016/09/01 23:18:22]

Acknowledged.

   optional int32 protocol_version = 2;
 }