Add Conjur step template with JWT authentication

[gl-johnson]

Background

We have a customer ask to provide a CyberArk-certified step template using short-lived credentials (via Generic OIDC Accounts feature) to authenticate Octopus workloads and retrieve secrets from CyberArk Conjur.

Results

This PR adds the aforementioned step template.

Pre-requisites

• 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).
• Version should be incremented, otherwise the integration with Octopus won't update the step template correctly
• Parameter names should not start with $
• 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).
• LastModifiedBy field must be present, and (optionally) updated with the correct author
• The best practices documented here have been applied
• 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

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Start Hyponome locally

docker pull ghcr.io/hnrkndrssn/hyponome:main
docker run --rm -p 8000:8080 -it ghcr.io/hnrkndrssn/hyponome:main

Review in Hyponome

[hnrkndrssn]

Thanks for your contribution @gl-johnson! Everything looks fine to me.

Note: I've only reviewed the script for any obvious errors, I've not tested the functionality as I'm not setup for this so I'm relying on that testing has been done before this submission.