Applies to: #719

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.

App name is restricted to 24 chars and regex pattern now also restricts first char to lowercase letter

In next PR I plan to update Angular to 1.5 and compiler to a new
release. This is a cleanup that is prerequired to do this. There's a
bunch of small fixes here, like unused variables removal or documenting
with JSDoc.

This is in preparation for release. After we do this, incompatible
changes to the api will be forbidden.

Layout on deploy page

As per spec:
https://raw.githubusercontent.com/kubernetes/dashboard/master/docs/design/mockups/11-11-2015/14_deploy%20more.png

This also does:
* unify styles of port mappings and label inputs
* make label input not auto-delete rows that are empty - this is because
  I find such behavoir too aggresive (e.g., when you erase the text by
  hand you go to previous page when the row is being deleted)

This is to be able to run when the application is rooted not at the
domain name. E.g.,
http://localhost:8080/api/v1/proxy/namespaces/kube-system/services/kubernetes-dashboard/#/replicasets

This validates application name asynchronously on the server. Validation is synced with namespace select :)

This is because name does not make sense in the YAML upload form.

This is because new compiler version has new type inference, which is
more strict.

The UI is as specified in the mocks, except for the names of the fields.
I decided to go with what is in the API.

Everything is extensively tested. I also added some tests for previously
untested cases.

The reason for doing this is the fact that namespace selection does not
make sense in case of uploading YAML. This should be only in deploy from
settings.

This change handles replica set description end-to-end: saving in on the
deploy form and then displaying. It also handles replica set endpoints.
I also attempted to write tests for the go code, but this change grew
too much. I'll do this later.

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.

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.

The cards now display mostly fake data, but they look more complete. The
backend will be implemented soon.