Add step template for creating an annotation in Azure Application Insights based on Azure CLI and RBAC instead of an API Key

[NielsDM]

Background

As Azure will stop supporting the function to annotate releases based on API keys and only supports RBAC to create annotations. There for I created this step template so an annotation can be created with a service principle.

Results

Create an annotation with Azure CLI and Role-Based Access Control.

Before

After

Pre-requisites

• [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
• [X] The best practices documented here have been applied
• [X] If a new Category has been created:
  • [X] An image with the name {categoryname}.png must be present under the step-templates/logos folder
  • [X] The switch in the humanize function in gulpfile.babel.js must have a case statement corresponding to it

Fixes # . If there is an open issue that this PR fixes add it here, otherwise just remove this line