Upgrade protobuf go package dependency to v3

[pooneh-m]

Upgrade go package dependency to 1.3.2 for golang/protobuf in go.mod and ran go mod vendor.
The additional changes to pborman/uuid are due to outdated vendor.

[google-oss-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: pooneh-m
To complete the pull request process, please assign
You can assign the PR to them by writing /assign in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[agones-bot]

Build Succeeded 👏

Build Id: e3b80d01-d46a-4365-92e1-1565f39e3c95

The following development artifacts have been built, and will exist for the next 30 days:

• image: gcr.io/agones-images/agones-controller:1.0.0-c117e18
• image: gcr.io/agones-images/agones-sdk:1.0.0-c117e18
• image: gcr.io/agones-images/agones-ping:1.0.0-c117e18
• Linux C++ SDK (build): agonessdk-1.0.0-c117e18-linux-arch_64.tar.gz
• SDK Server: agonessdk-server-1.0.0-c117e18.zip

A preview of the website (the last 30 builds are retained):

• https://c117e18-dot-preview-dot-agones-images.appspot.com/

To install this version:

• git fetch https://github.com/GoogleCloudPlatform/agones.git pull/1027/head:pr_1027 && git checkout pr_1027
• helm install install/helm/agones --namespace agones-system --name agones --set agones.image.tag=1.0.0-c117e18

[markmandel]

The previous go protoc package (1.2.0) supported proto 3, so I'm not sure why we are upgrading? Is there a strong reason to do so?

Given that were aiming for 1.0 in the next release, I'm thinking we shouldn't do this to maintain a stable, known system, unless there is a very good reason to do this?

[pooneh-m]

Makes sense. I am introducing an allocator API proto definition and getting dependency to the latest proto package, but it is not necessary.