Fix issues found during submission api wrapper contest

[callmekatootie]

Two issues reported during submission api wrapper contest:

• Missing definitions:

# request headers
    - $ref: '#/parameters/IfNoneMatchParamHeader'
    - $ref: '#/parameters/IfModifiedSinceParamHeader'

• For review type creation, id field is marked as a required input in swagger, when in fact, it is auto generated.

[callmekatootie]

Issues reported during wrapper contest (Reviews)

• POST /reviews returns 200 as status code. Swagger says 201. Swagger needs correction.
• For reviews resource, swagger specification says that scorecardId can be an integer or string. Code also says so, but since we did not specify the schema when interfacing with ES, ES has taken the schema to be that of an integer. Update the code and the swagger specification to indicate that scorecardId needs to be an integer
• ReviewerId needs to be either number or string. However, when a non number and non string value is passed (for example a boolean value), the error received is that reviewerId should be a number. It should be reviewerId should be either a number or a string instead

[callmekatootie]

Review Summations:

• isFinal field exists in code but not in swagger

[callmekatootie]

Submission:

• PUT /submissions/{submissionId} says type field is required. Code does not. Update swagger
• GET /submissions does not talk about filter query parameters related to review (such as review.score and review.typeId). Code supports it
• GET /submission does not document that the response might contain legacySubmissionId, legacyUploadId and submissionPhaseId

[callmekatootie]

Contest Launched for remaining fixes: http://www.topcoder.com/challenge-details/30098900/?type=develop

[callmekatootie]

PR ready: #127

[callmekatootie]

PR merged. Closing ticket.