feat(security): add cookie-auth support

[matteomazza91]

PR checklist

• Read the contribution guidelines.
• Ran the shell script under ./bin/ to update Petstore sample so that CIs can verify the change. (For instance, only need to run ./bin/{LANG}-petstore.sh and ./bin/security/{LANG}-petstore.sh if updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates). Windows batch files can be found in .\bin\windows\.
• Filed the PR against the correct branch: Default: master.
• Copied the technical committee to review the pull request if your PR is targeting a particular programming language.

Description of the PR

It adds cookie-auth support as specified in the spec

It relates to issue #208

Test performed

run the codegen with -DdebugOperations=true on an OpenAPI spec file with cookie auth.

input:

...
securitySchemes:
  user_creator:
    type: apiKey
    in: cookie
    name: JSESSIONID
....

output:

...
"authMethods" : [ {
    "name" : "user_creator",
    "type" : "apiKey",
    "hasMore" : false,
    "isBasic" : false,
    "isOAuth" : false,
    "isApiKey" : true,
    "vendorExtensions" : { },
    "keyParamName" : "JSESSIONID",
    "isKeyInQuery" : false,
    "isKeyInHeader" : false,
    "isKeyInCookie" : true,
    "isCode" : false,
    "isPassword" : false,
    "isApplication" : false,
    "isImplicit" : false
  } ]
....

[wing328]

@matteomazza91 thanks for the enhancement, which looks good to me.

[jimschubert]

Looks good, I didn't run to try it out.

I wanted to comment that we discussed in the linked issue of possibly validating/verifying that the spec (if 2.0) supported the cookie API feature. We decided that it would be better to validate on generation by default, which avoids lots of conditional branches evaluating feature sets between spec versions. I have added the validation on generation as part of #251.