WIP: GoDaddy Contributions

Corrected generateModelDefinition() to scan for model references in remote accepts, returns, errors, and nested models
Changed addRoute() to honor X-Forwarded-Host
UI/UX cleanup for SwaggerUI
	Add support for toggling Model and Schema, instead of just expanding
	Added guard against null mockSignature
	Added support for toggling Model and Schema, and added support for primitives in StatusCodeView
	Changed to hide the message-bar when no message
	Changed to use defaultValue, if present, for sampleValue
	Changed to use relative path for images/throbber.gif for mounting into apps at different levels
	Collapse and label responseModel description by default
	Correct description of collections of object and nested
	Corrected to avoid showing invalid Model and Model Schema is missing or void
	Corrected to load images relative to swaggerRoot, for nested context root
	Corrected to work when loading resources from file://
	Ensure Response Content Type is shown regardless of Response Class
	Omit divs for info.title and info.description if they're absent
	Removed 'Implementation Notes' label since it's just noise, widened Resource expansion anchor to full label

**Tasks**
 - [x] https://github.com/strongloop/loopback-explorer/pull/58
 - [ ] `X-Forwarded-Host` header
 - [ ] `apiVersion` and `swaggerVersion`
 - [ ] UI customization (`contentWell`)
 - [ ] describe models for accepts and nested returns
 - [ ] response and error messages
 - [ ] additional param metadata like `pattern` and `enum`
Swagger provides two ways for specifying the response type:
 1. globally in `operations[].type`
 2. per-response-code in `responseMessages[].responseModel`

![screen shot 2014-10-14 at 13 36 43](https://cloud.githubusercontent.com/assets/1140553/4628393/9c2eb906-5396-11e4-9b78-5d68f8e1fe45.png)

In the screenshot above, `operations[].type` is displayed as "Response Class" at the top, `responseMessages[].responseModel` is displayed in "Response Model" inside "Response Messages" section at the bottom.

I'll submit a pull request that keeps the response model in both places. We can discuss what's the best solution in the PR.