Include go dependencies in developer-guide.md

[alexandraj777]

Easier for new-to-go developers to get up and running.

Looks like Google protobufs might also be a dependency?

---

This change is 

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[k8s-ci-robot]

Hi @alexandraj777. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[alexandraj777]

SigOpt should now have a signed CLA in place! Per the instructions, my work email address should be on the google group associated with the agreement

[alexandraj777]

/assign @hougangliu

[alexandraj777]

/assign @richardsliu

[richardsliu]

/ok-to-test

[hougangliu]

/lgtm

[alexandraj777]

@hougangliu thank you for approving! This is my first time committing to this project, what are the next steps I should take here? I know signing a CLA was a blocker, and it looks like the Google CLA system finally shows my corporate CLA on the dashboard.

[richardsliu]

@alexandraj777 Can you reply to the PR with "I signed it!"?

[alexandraj777]

I signed it!

[richardsliu]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: richardsliu

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [richardsliu]

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

[googlebot]

CLAs look good, thanks!

[alexandraj777]

@richardsliu I figured it out! The email address on my commit was my personal email address, but the email address on my CLA was my work email address. This has been fixed, and force pushed to this branch. Mind re-approving for me?

[johnugeorge]

/lgtm

[richardsliu]

/retest

[richardsliu]

@alexandraj777 Looks like we're running into quota problems. I'll let you know once it gets resolved.

[richardsliu]

/retest