Make it easy to use the e2e tests to test upgrading a running master

by adding support for testing official release versions and writing a simple script to first bring up and test the old version before upgrading it and testing it again. Related to supporting in-place upgrades of masters (#2524).

The downsides of this are that by default it uses the e2e tests from HEAD, which may not be expected to pass on an old cluster, and that it uses the client binaries from head. I can send a follow-up to fix the client binaries issue, but don't have anything planned for supporting old e2e tests.

I'm not sure how our Jenkins setup is configured, but it'd be nice to get something along these lines added to it in the future.
Thinking out loud: rather than this shell script, what if e2e.go took a list of versions and did tests in a loop? Like
for `go run hack/e2e.go -up -versions=v0.6.0,build -test -down` I'd expect to get the sequence of actions

```
get version v0.6.0
up
run tests
build HEAD
push
run tests
down
```

But I suspect even this won't be enough; you may want to test against two different non-official builds... I guess that can come later.