WIP: Assert actual matches expected using dynamic assertions

[shrink]

Assertions in a workflow are valuable, especially in workflows for validating the behaviour of an action. There's a fantastic action Assert Action however it is limited to a fixed set of string based assertions.

• A Workflow can include custom assertions defined in the repository
• expected, actual

- uses: pr-mpt/actions-assert
  with: 
    expected: "Hello, World!"
    actual: "${{ steps.message.outputs.greeting }}"
    assertion: "is-equal"
    type: boolean|string|int|json
    each: true # should we iterate through a new line delimited list

Features

• Configurable type (integer, boolean, string)
• Accepts external assertions from npm packages and the repository
• Results include messages

Assertions

• Pattern match Regular expression pattern match assertions#6
• Status code (cURL) HTTP Status Code match assertions#7

Questions

• An assertion might have more complex configuration, how do we provide that? Some sort of hacky nested json driven with for config? e.g: an http request might require a bearer token -> environment variables