chore: automate release process

[WilliamBergamin]

Summary

This PR aims to automate the release process making it easier and simpler for maintainers to cut releases

Testing

Once this PR is merge we can manually run the release process in dry run and against test.pypi.org

Category

• slack_sdk.web.WebClient (sync/async) (Web API client)
• slack_sdk.webhook.WebhookClient (sync/async) (Incoming Webhook, response_url sender)
• slack_sdk.socket_mode (Socket Mode client)
• slack_sdk.signature (Request Signature Verifier)
• slack_sdk.oauth (OAuth Flow Utilities)
• slack_sdk.models (UI component builders)
• slack_sdk.scim (SCIM API client)
• slack_sdk.audit_logs (Audit Logs API client)
• slack_sdk.rtm_v2 (RTM client)
• /docs (Documents)
• /tutorial (PythOnBoardingBot tutorial)
• tests/integration_tests (Automated tests for this library)

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.
• I've run python3 -m venv .venv && source .venv/bin/activate && ./scripts/run_validation.sh after making the changes.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.15%. Comparing base (618808f) to head (352d4ed).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1781   +/-   ##
=======================================
  Coverage   85.15%   85.15%           
=======================================
  Files         115      115           
  Lines       13069    13069           
=======================================
  Hits        11129    11129           
  Misses       1940     1940           

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

[zimeg]

@WilliamBergamin Once more, this is an awesome changeset 👾

I left a comment with thought on commit messages and share similar thoughts as in slackapi/bolt-python#1394 but please feel free to update these to what seems right of course!

[zimeg]

💡 thought: I'm a fan of this format, but wonder if we might want to include the package name here as well?

git commit -m 'chore(release): slack-sdk 1.2.3'

🗣️ ramble: This might not be the right convention, but I am thinking about adjacent projects in this comment...

[WilliamBergamin]

I think we can keep this simple for now 💯