Add non-semver-tags input argument

[nwiltsie]

Description

This closes #17 by adding a non-semver-tags argument. If that argument is given any value, the docker/metadata-action gets the additional docker tag format type=match,pattern=v(.*),group=1. That tag format will ensure that any git tag of the form vX will result in a docker tag of the form X.

I tested this with my trusty docker-internal-tests repository. When I had this workflow...

    steps:
      - uses: uclahs-cds/tool-Docker-action@dev
        with:
          non-semver-tags: true

... and tagged it as v0.0.5c, the workflow ran successfully and pushed the corresponding tag.

[!NOTE] As you can see I technically used the dev branch and not nwiltsie-arg-for-non-semver, but that's just to make future testing with that repository easier. The workflow logs show that it used 87e99e2cb9d0588d91f4597b02dc1647e2722f5d.

When I removed the argument and tagged it as v0.0.5d, it failed with the error from #17.

Closes #17

Checklist

• [x] This PR does NOT contain PHI or germline genetic data. A repo may need to be deleted if such data is uploaded. Disclosing PHI is a major problem.
• [x] This PR does NOT contain molecular files, compressed files, output files such as images (e.g. .png, .jpeg), .pdf, .RData, .xlsx, .doc, .ppt, or other non-plain-text files. To automatically exclude such files using a .gitignore file, see here for example.
• [x] I have read the code review guidelines and the code review best practice on GitHub check-list.
• [x] I have set up or verified the main branch protection rule following the github standards before opening this pull request.
• [x] The name of the branch is meaningful and well formatted following the standards, using [AD_username (or 5 letters of AD if AD is too long)]-[brief_description_of_branch].
• [x] I have added the major changes included in this pull request to the CHANGELOG.md under the next release version or unreleased, and updated the date.