Now raw data is gathered on the backend and rendered on the frontend.

Now variables are in variables.css in frontend directory. Previously they were in assets, which was wrong because it caused copy to production image.

They just have been recently added. It allows us to delete some code.

This change adds linter for styles to the project and updates all styles
to conform with the default set of rules.

This should help us maintain a little bit more consistency in our
styles.

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

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.

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.