cmd: use binaryproto input and output invocations

RTDs should read binaryproto-encoded Invocation protos to ensure better
backward and forward compatibility. Here's my argument for that from a
year back: go/cros-binary-proto
JSONpb makes it hard to change field names and to introduce new enum
values while maintaining compatibility.

TEST=ran it locally

Change-Id: Ia4a001465b59c8cde942031e1b0a70bd28d7d6a3
Reviewed-by: Prathmesh Prabhu <>
Commit-Queue: Sean Abraham <>
Tested-by: Sean Abraham <>
2 files changed