Adding new lambda template that uses IAM role instead of AWS account.

[twerthi]

---

Step template checklist

• [X] Id should be a GUID that is not 00000000-0000-0000-0000-000000000000
  • NOTE If you are modifying an existing step template, please make sure that you do not modify the Id property (updating the Id will break the Library sync functionality in Octopus).
• [X] Version should be incremented, otherwise the integration with Octopus won't update the step template correctly
• [X] Parameter names should not start with $
• [X] Step template parameter names (the ones declared in the JSON, not the script body) should be prefixed with a namespace so that they are less likely to clash with other user-defined variables in Octopus (see this issue). For example, use an abbreviated name of the step template or the category of the step template).
• [X] LastModifiedBy field must be present, and (optionally) updated with the correct author
• [ ] If a new Category has been created:
  • [ ] An image with the name {categoryname}.png must be present under the step-templates/logos folder
  • [ ] The switch in the humanize function in gulpfile.babel.js must have a case statement corresponding to it

Fixes issue where existing Deploy Lambda template requires the use of an AWS account. This one uses an IAM role.

[twerthi]

Implemented suggested changes (name and description).

Added variable replacement functionality, new code review recommended.

ID values may have changed as I just re-exported the template versus updating the JSON here. It's new so it won't affect any existing implementations.