Now it parses kubeconfig files when present

Try running `./dist/amd64/dashboard`. It should get info from your
kubectl file and use it.

With this we'll be able to do generic stuff, e.g., deletion or YAML
edition.

After this is merged I'll be working on "commonization" of things.

This includes a huge refactor to extract pod list common code from RC
deatails to a separate directory. With this, though, it can be reused in
lots of places (e.g., in Daemon Sets).

Frontend will follow soon.

This is initial version of this view. Will iterate.

Plus stub for details page.

This is long, but mostly boiler plate. Please sync and check how it
works.

What I did here:
* I copied old RC list code
* Changed all directives to angular 1.5 components
* Removed custom CSS styles
* Added missing tests

What is missing:
* Zerostate page
* responsiveness (this is a problem of the common component)
* Documentation

This looks consistent across all our pages. Best pull this branch to
test.

It can be used on pages to display stuff.

Initial, but working, implementation. Will evolve in future. You can
check this out on /api/v1/workloads

I'll be developing new one, which will use the common framework. I hope
it to be smaller.

This one will get deleted once new one is done. With this renaming I'll
be easy.

The api modernization is to allow for testing.

With this when I'll be implementing Workloads page I'll just load
Pods/Services/Nodes once and pass it around for
RC/ReplicaSet/DaemonSet/etc processors

Re #666

Re #630

* Now resource cards are in a list and have columns
* Columns are sized according to spec
* Tell me whether something needs more documentation

Fix relative time filter

Now this directive works on window resize and on all pages (RC details
in particular).

This PR also fixes issues on details page which didn't handle small
screens correctly.

Fixes #625

This is initial PR on this. It uses quite a few interesting new
techniques, so I want throughful feedback.

1. This uses angular 1.5 Components and multiple transclusion
2. I propose here the way of writing Components. Basically you create
foo_component.js file and add component config and controller there.
3. See multiple transclusion - it is awesome

Re #630

Crash if cannot get server version from initial request. Fail with
verbose error message.

Parially addresses: #620

We've been missing them for so long...

This is initial framework with dummy example of an action bar. It'll be
extended further later. But it works now.

Having actionbar in a view of a state forces separation of concerns.
I.e., devs will not put action bar and a list of resources in one
place.