WIP: GoDaddy Contributions

Broader and deeper support for Swagger capabilities, including 1.2
	Upgraded to generate specs based on Swagger 1.2
	Add indication of response being a collection
	Added description for 200 responseMessage
	Added missing docs for errors and notes
	Added support for automatically re-joining long strings split into arrays in specs for description, notes, and message values
	Added support for errors property to specify possible errors that can be returned
	Added support for multiple responseMessages from Swagger 1.2
	Added support for notes per API
	Added support for primitives in StatusCodeView
	Added support for return types as Arrays instead of Strings
	Avoid adding empty description for each API
	Changed to possibly pull model description from ctor.settings
	Corrected addDynamicBasePathGetter() to honor x-forwarded-proto in order to support reverse-proxy from https to http
	Corrected default for consumes+produces
	Corrected generateModelDefinition() to scan for model references in nested models, remote returns, and errors
	Corrected prepareDataType() to handle collections and nesting, and changed to always and only use responseMessages

Automatic conversion of response bodies to XML, when requested via Accept: header
	Added error-handling when unable to generate XML
	Added support for automatically converting to XML, if requested via Accept
	Better support for alternate Content-Types
	Configured pretty-printing and date conversion to ISO for XML responses
	Corrected XML handling when root is an Array
> @ritch If I understand your intentions correctly, we will use type property in remoting metadata, and then convert it to responseModel property in strongloop/loopback-explorer#52. That way the strong-remoting part is not tied to Swagger, the DSL stays consistent, and we can support both Swagger 1.2 and 2.0 in the future.

exactly