Add docs on kubectl & helm access to pilot hubs

[yuvipanda]

Fixes #75

[choldgraf]

this looks great @yuvipanda - thanks for improving this! Perhaps @GeorgianaElena can have a quick look to see if anything is missing since she recently went through this process?

Non-blocking on this PR: I was wondering what you thought about a 2i2c practice of writing one sentence per line in documentation. This sometimes leads to long-ish lines, but I've found that it makes patching the markdown files easier to do via UIs such as GitHub's interactive editor, and is also a fairly intuitive decision-point to use rather than "how many characters does my line have". Curious what you think about that.

[yuvipanda]

Thanks @choldgraf!

She had only gone through the process of setting up for farallon hubs, nothing on Google cloud yet. We can use this as basis and modify as we go.

I mostly break lines wherever my editor does, and I think most text editors can be configured to break lines and reflow them as needed. This seems more automatic to me than breaking per sentence, since we would have to do that manually.

[choldgraf]

sounds good 👍

re: lines - the main benefit I've found is that because GitHub's interactive UI requires you to add a suggestion to only one line, rather than multiple lines, this is where having "one sentence per line" is helpful. It's nothing crucial right now (and in the future we may be able to just use an auto-formatter like https://github.com/executablebooks/mdformat) but in the future we'll need to find practices that make editing and changing the markdown as easy as possible.