chore(release): tag version 3.0.0

[zimeg]

Summary

This release tags the changes to main as v3.0.0 🏁 ✨

Notes

• Milestone: https://github.com/slackapi/slack-github-action/milestone/21 🔮

Requirements

• 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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.86%. Comparing base (e45cb89) to head (35a67c2).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #575   +/-   ##
=======================================
  Coverage   99.86%   99.86%           
=======================================
  Files           7        7           
  Lines         718      718           
=======================================
  Hits          717      717           
  Misses          1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[zimeg]

📚

slack-github-action/.github/maintainers_guide.md

Lines 45 to 79 in 963b979

	### Releasing
	1. Check the status of this project's GitHub [Milestone](https://github.com/slackapi/slack-github-action/milestones) to be released for issues that should be shipped with the release.
	- If all issues have been closed, continue with the release.
	- If issues are still open, discuss with the team about whether the open issues should be moved to a future release or if the release should be held off until the issues are resolved.
	- Take a look at all issues under the Milestone to make sure that the type of issues included aligns with the Milestone name based on [semantic versioning](https://semver.org/). If the issues do not align with the naming of the Milestone (ex: if the issues are all bug fixes, but the Milestone is labeled as a minor release), then you can tweak the Milestone name to reflect the correct versioning.
	2. Checkout a branch for the release:
	```sh
	$ git checkout -b v1.2.3
	```
	3. Update the version in `package.json` and `package-lock.json` and examples:
	```sh
	$ npm version <major|minor|patch> --no-git-tag-version
	```
	4. Run all tests with the latest dependencies to make sure tests pass:
	```sh
	$ npm ci
	$ npm test
	```
	5. Commit the changes on your release branch and open a pull request with relevant labels:
	```sh
	$ git commit -m "chore(release): tag version 1.2.3"
	$ git push -u origin v1.2.3
	```
	6. After merging these changes into `main` create a new [release](https://github.com/slackapi/slack-github-action/releases/new) with a new tag - `v1.2.3` - on publish. Include relevant changes in the release notes!
	7. Rebuild [documentation](#docs) with the latest versions.
	8. Once released, make sure to close the relevant GitHub Milestone for the version you released.