updated CI to use latest version of this action when running tests

[stevengill]

Summary

updated CI to use latest version of this action when running tests

Requirements (place an x in each [ ])

• I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.

[stevengill]

Alright, this is ready for a review @filmaj @seratch

I broke out the botToken and webhook integration tests into their own jobs. Added a job for unit tests.

The webhook job does some normalizing of the github paylods (between push and pull request) and sends the normalized object to workflow builder. A pretty nice usecase to share I think.

We may want to add a unit test + integration test for incoming webhook as well here.

[stevengill]

Also, @filmaj the unit test job outputs the entire payload of the event. I feel like this shouldn't be happening. See the npm test section in https://github.com/slackapi/slack-github-action/runs/4318381157?check_suite_focus=true

[seratch]

Thanks for working on this!

[filmaj]

Hey this is awesome! Love the integration test jobs you wrote up, left a few comments on potential tweaks.

As for the unit test output, I believe this is happening because in one of the error paths in the code for the action, we console.log the entire payload, which itself may be loaded from a GitHub Action event (which furthermore comes in via the @actions/github module). So in our situation here: since the CI for this Action is itself running via GitHub Actions, the relevant GitHub-Actions-specific environment variables are present, so the pull request GitHub event payload info is loaded up when running the unit tests in CI 😆

We could comment out the console.log in the error path as one potential solution. Or leave it as-is. I don't think it's a big deal either way. The unit tests exercise that error path, so I think it is expected.