Fixing bug introduced by latest version of Liquibase

[twerthi]

---

Background

Two things exist in this PR.

1. I added the code to support SqlAnywhere, but forgot to add the option to the drop down menu. This PR adds that option.
2. It looks like Liquibase updated the batch file used for execution to include a find command when using Windows. The location of the find executable, c:\windows\system32, is not part of the standard PATH environment variable. This version adds that location to the executing PowerShell session when executing in Windows.

Results

Users are now able to select SqlAnywhere from the drop down and perform database migrations to it. Windows executions no longer fail due to find not being a valid command.

Before

Users could not deploy against SqlAnywhere and Windows executions were failing due to find not being found ... no pun intended.

After

Users can now select option and Winows executions no longer fail.

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

[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