Update to Swagger 1.2. Fixes #11, #8, #7.

Changes in this PR:

* Moved `public` (swagger UI) out of this module and required `swagger-ui` as a module in `package.json`.
* Added `swaggerDistRoot` option so users of the API Explorer can override any part of the UI (styles, JS, HTML).
* Compatibility with Swagger 1.2 ([spec](https://github.com/wordnik/swagger-spec/blob/master/versions/1.2.md)) ([transition guide](https://github.com/wordnik/swagger-spec/wiki/1.2-transition))
* Model schemas are now correctly populated.
* An `accessToken` can be provided via the header input.

When this is merged, it should be safe to remove `strong-remoting/ext/swagger`, the associated test, and `app.docs()`.

Fixes #7, #8, #11.
I think you misunderstood my comment. The idea was to not modify the route, but return the `accepts` in the format needed by swagger.

```js
var accepts = routeHelpers.convertAcceptsToSwagger(route, classDef);

var apiDoc = {
  // ...
  parameters: accepts.map(routeHelper.acceptToParameter(route))
  // ...
}
```

An even better solution may be to call `acceptToParameter` from `hackAcceptsDefinition`.

```js
function buildParameters(route) {
  // add ctor arguments
  // filter out computed arguments
  // for each argument: convert the type to Swagger, convert the argument to Swagger parameter
}

// later
var apiDoc = {
  // ...
  parameters: buildParameters(route)
  // ...
}
```

Anyways, I guess this is rather subjective. If you don't think my proposal will make the code better or you don't think it is worth the effort, I can live with the current version too.