Filtering CI Checks

This pull request does the following:

• Adds a new input option called ignored_checks which accepts a comma separated list of checks that will be ignored when determining if a deployment can continue.
• Updates the checks input option to support more than just all or required. You can now pass in a comma separated list of CI job names to explicitly include as required checks from this Action's point of view.

Read through the related issue to get even more context around these changes

related: #321

Examples 📸

Adding Custom checks with no ignored_checks and a check fails

Configuration:

- uses: github/branch-deploy@ignored-contexts
  id: branch-deploy
  with:
      checks: 'test1,test3' # we only care about the checks named `test1` and `test3`
      ignored_checks: '' # no checks are allowed to be ignored explicitly

Result:

Adding Custom checks with no ignored_checks and it passes

Configuration:

- uses: github/branch-deploy@ignored-contexts
  id: branch-deploy
  with:
      checks: 'test1' # we only care about the check named `test1`
      ignored_checks: '' # no checks are allowed to be ignored explicitly

Result:

No Custom checks but multiple ignored_checks and it passes

This example shows how to use ignored_checks to ignore a certain check. This will allow for deployments even if a check is required via branch protection settings for merging.

Configuration:

- uses: github/branch-deploy@ignored-contexts
  id: branch-deploy
  with:
      ignored_checks: 'test2,test3' # these two checks are ignored and deployment will be allowed even if they are failing

Result: