Reported here envoyproxy/go-control-plane#407

The dependency on OT protos from Envoy protos means that exporting just the @envoy_api protos becomes insufficient for Go to use the protos generated by tools/api/generate_go_protobuf.py

The immediate problem is that the OT protos use logs as an import path which conflicts with the std lib, but on further inspection it's clear that the OT protos are not being synced over, and are not readily available via the regular Go tool chain.

Note sure what the best way is to solve this: either export the OT protos alongside the existing protos or teach the script how to wire up the OT protos in such a way that we can resolve the dependency issue.

cc @kyessenov