With this we can cross compile. The build usage is backwards compatible,
everything works as before. The addition is that there are some tasks
with :cross suffix that do cross compilation.

Now dist folder is separated by architecture.

Sample output from ./build/run-gulp-in-docker.sh
docker-image:canary:cross

```
gcr.io/google_containers/kubernetes-dashboard-arm64          canary
241c95709a4b        About an hour ago   35.04 MB
gcr.io/google_containers/kubernetes-dashboard-amd64          canary
3ccd83107b69        About an hour ago   35.37 MB
gcr.io/google_containers/kubernetes-dashboard-arm            canary
4533431c6a73        About an hour ago   29.03 MB
gcr.io/google_containers/kubernetes-dashboard-ppc64le        canary
3bfa0191f041        About an hour ago   35.53 MB
gcr.io/google_containers/kubernetes-dashboard-amd64          v0.1.0
3351515d6e5e        About an hour ago   35.44 MB
gcr.io/google_containers/kubernetes-dashboard-arm64          v0.1.0
45e4a971bfc3        About an hour ago   35.44 MB
gcr.io/google_containers/kubernetes-dashboard-arm            v0.1.0
1057ae5d74e5        About an hour ago   35.44 MB
gcr.io/google_containers/kubernetes-dashboard-ppc64le        v0.1.0
d587f991ac08        About an hour ago   35.44 MB
```

Added check to prevent display of replica set list page when there are no replica sets.

With this change I've gone through all ESLint rules at:
http://eslint.org/docs/rules/ and added all of them that I feel make
sense to the project.

This will allow us to focus on business logic of our code, rather than
on style discussions, which are now better guarded thanks to ESLint and
clang-format.

On the final note: it does not matter what concrete lint rules are
enforced (e.g., semicolons or nor). The important part is that they are
enforced by a tool and we do not spend time dicussing about them.

Addresses: #66

The implementation consists of backend code and sample frontend view
that dumps the data into an ugly looking table. Subsequent changes will
implement frontend so that things look pretty.

This change connects replica set list and detail views and applies
RESTful conventions to the API.

Now API and app URLs follow RESTful API conventions. This change is also
an example of how views hould be connected. See state params and state
name exports.

This is a required change because with dot case we cannot reference
other modules inside JSDoc `@type` annotations. For example, if you want
to reference `@type {./deploy.controller.FooType}` does not work,
because the compiler does not know whether `deploy` is a module or
`deploy.controller`. Changing dot case to undersocre, camel or dash case
solves this problem.

I decided to go with underscore case because this is what golang uses
(e.g., `foo_test.js`) so we'll have higher similarity of backend and
frontend codebases.

This is all frontend boilerplate for the view.

Per discussion in: https://github.com/kubernetes/dashboard/issues/65

This change does only renaming, no functional modifications.

1. This is a model for mocks:
https://github.com/kubernetes/dashboard/blob/master/designs/11-11-2015/16_card%20variations.png
2. Did little renaming (used the word "microservice") until we agree what the list exactly shows.
3. The implementation is very basic and will evolve over time.

This is all boilerplate that sets up the page, with some example
content. This change alsu updates angular material to newer version.

This change is mostly boilerplate for the two views and cleanup of test
code that has been laying around.

This is a chrome that has Kubernetes-like color palette.

This change implements initial version of the chrome. It uses ui.router
for routing and state management. The reason to use this router is the
fact that it is more flexible than stock one. It also resembles Angular2
router, so hypothetical migration should be easier.

This change modifies a lot of JS, but this is only to prove that the
code works. Later changes will cleanup the JS more.

With this change advanced optimizations of the Closure Compiler work and
produce working output.

This is a sample Angular application written in ES6 with modules. It has
sample unit and integration tests. It was generated with a help of
Yeoman.

Don't mind what the application does right now. I'll use it for a next
few days to verify that build system is working. Then it will be
revamped.