To test this edit a pod in a list.

Missing things that will be done in next PR:
* make the menu and popup look pretty
* make json editor work on serve:prod (now images are missing)

Now it is renamed and minified. JS side dropped from 2.5MB to 500KB.

Previously it did't work on my machine. Now it does.

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
```

* now it is possible to build and push images to gcr.io with gulp
* there's yaml file to run the dashboard in your cluster with kubectl create -f

This is to prevent flakyness in our travis infrastructure.

BREAKING CHANGE: Now node 4 is required to build the project. This is
because protractor 3 requires is. I decided to make the switch now,
because it would happen anyway at some point.

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

This change reformats all files according to clang-format rules (the
same that Angular JS has) and forces the files to comply with the
formatting.

After this change local development servers do not serve from the repository root. The reason is that the root contains .git folder which may include confidential information.

This change makes it possible to run tests, integration tests and lint
on Travis CI. It also prepares a special Gulp task to perform the same
activities locally. This is handy when, e.g., sending a pull requrest.

Next change will actually implement some tests for the backend.

This setup autoreloads backend process on source change and ensures that
there is only one process running.

Follow up would be to wire this setup with browser sync to proxy API
calls to the backend.

This is build integration commit after my recent set of separate changes with standalone tasks. Now, every task works and produces reliable output.

Added a few simple rules to the linter and fixed all errors through the
codebase. This will allow to wire it up to some automatic checks.