Default only string fields to email type

Only default fields named email to email type when they are strings
changed swagger version to 1.2 (from 1.1)
Each operation element can contain an optional responseMessages value. This was renamed from errorResponses.
The parameters has been updated to support JSON-schema v4 format. format property is used for more fine grained type declaration
Each element in the responseMessages array contains an integer code and string message field. Previously, the analogous errorResponse attributes were named code and reason respectively.
The dataType field has been renamed to type for consistency with the JSON-schema v4 draft spec.
The allowableValues field has been absorbed into an enum for LIST type, and minimum + maximum for ranges
The API Declaration supports a `produces` array and `consumes` array, which are array of strings. These apply to all operations in the API unless overridden at the API level
Elements in the operations array can contain `produces`, this value overrides any existing values at the API Declaration
Using items->$ref instead of item->type as per swagger 1.2 spec for return model.
Adding PassThrough class to serve files outside your web root, including secure downloads
Explorer class to replace Resources
swagger ui for 1.2 spec testing
Including Explorer in the scope
Remove slash from resource path.
New method for finding all routes after excluding set paths and http methods
Updated swagger to load resources.json by default. And allowed HTTP PATCH
First functional version of Explorer. For usage example look at `public/tests/param` folder