Improve support for custom workflow statuses, in addition to built-in statuses about prwatch-action HOT 1 OPEN

It appears as though there's no way to determine what is a "backward" status move from Jira API's issue status list unless one is using Jira Server: https://confluence.atlassian.com/jirakb/how-to-re-order-statuses-675385085.html

It was my original hope that it would be possible through the API to determine an issue's relative position to CONFLICT_ISSUE_STATUS in a workflow.

For example if a jira project had the following workflow

Status 1                -> Status 2 -> Status 3 -> Done
CONFLICT_ISSUE_STATUS                  Current 

Status 1 could be considered a "Send back" from Status 3 because it comes earlier in the sequence.

But the reality is the Jira status can be listed in any order; particularly if they are user-defined. i.e. a workflow has no concept of forward and backward motion.

One potential solution to this problem would be to allow users of this action to declare their project's workflow order in their YAML file

name: Monitor Pull Requests
jobs:
  monitor:
    name: Monitor
    runs-on: ubuntu-latest
    steps:
      - name: Monitor
        uses: acaloiaro/prwatch@v1
        with:
         workflow: Status 1, Status 2, Status 3, Done 

from prwatch-action.