Make first alpha deploy

The transit work has progressed quite a bit. So far we are able to import some GTFS feeds (not all, probably, as they seem to expose quite some different behaviour) and run queries against these feeds.
The queries do not resemble actual results, since all available trips over the course of the year are considered as running every day and we cannot wrap around the midnight boundary.

Still, I feel it is time to bring this project into prototype status. To do so, we need to clean up a bit of the current state and make the full project deployable.

## Clean-Up

Frontends for both debug and earliest arrival service should be running. Right now the earliest arrival plugin uses npm, the debug map is started via a SimpleHTTPServer. We should make this into a uniform server architecture that allows both frontends to be working alongside in npm server environment.

- [x] frontends unified

The URLs are currently hardcoded / the bundling stuff is removed. We should uglify the frontend again and update the bundle creation mechanism. Hardcoded strings should be pulled out into a source configuration.

- [x] removed hardcoded strings
- [ ] uglify frontend source

## Make Deployable

- [ ] Step 1: look how other projects are deployed
- [ ] Step 2: ?
- [ ] Step 3: Profit!

## Publish Binaries to NPM

- [ ] Manually publish the Js part of the package to npm, npm publish transit

Review how the debug map currently starts through SimpleHTTPServer and how the earliest-arrival frontend uses npm, then inspect the existing frontend bundling and the `npm publish transit` package path. The issue does not name files or tests; done means the full project has a defined deployment flow, the frontend is uglified, and the JavaScript package can be published to npm.

Written by the indexing model from the issue text.