Created by: sebastien-rosset

The HTTP signature auth mustache template should be included only when the OAS document has the http-signature security scheme. I've seen some builds failing, I'm not sure how the merge to master was possible.

https://circleci.com/gh/OpenAPITools/openapi-generator/16032?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link

PR checklist

• Read the contribution guidelines.
• If contributing template-only or documentation-only changes which will change sample output, build the project before.
• Run the shell script(s) under ./bin/ (or Windows batch scripts under.\bin\windows) to update Petstore samples related to your fix. This is important, as CI jobs will verify all generator outputs of your HEAD commit, and these must match the expectations made by your contribution. You only need to run ./bin/{LANG}-petstore.sh, ./bin/openapi3/{LANG}-petstore.sh if updating the code or mustache templates for a language ({LANG}) (e.g. php, ruby, python, etc).
• File the PR against the correct branch: master, 4.3.x, 5.0.x. Default: master.
• Copy the technical committee to review the pull request if your PR is targeting a particular programming language.