feat: add authorship arguments to say_stream

[zimeg]

Summary

This PR adds icon_emoji, icon_url, and username authorship arguments to SayStream, AsyncSayStream, SetStatus, and AsyncSetStatus helpers to match the new authorship support added in slack_sdk v3.42.0 🚀

• feat: add authorship arguments to assistant threads and chat stream python-slack-sdk#1862

Testing

@app.event("assistant_thread_started")
def handle_thread(say_stream, set_status):
    set_status(
        status="thinking...",
        icon_emoji=":maple_leaf:",
        username="Charlie Brown",
    )
    stream = say_stream(icon_emoji=":maple_leaf:", username="Charlie Brown")
    stream.append(markdown_text="Dancing with snoopy dog!")
    stream.stop()

Category

• slack_bolt.App and/or its core components
• slack_bolt.async_app.AsyncApp and/or its core components

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 ./scripts/install_all_and_run_tests.sh after making the changes.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.30%. Comparing base (3319330) to head (0f85e13).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1502   +/-   ##
=======================================
  Coverage   91.30%   91.30%           
=======================================
  Files         228      228           
  Lines        7271     7271           
=======================================
  Hits         6639     6639           
  Misses        632      632           

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

[zimeg]

⚡ Similar changes might not be needed in Bolt JS with the subtracted arguments:

https://github.com/slackapi/bolt-js/blob/ba4deb6a8b39da43cef0452d7541bcfcc3f3527a/src/context/create-say-stream.ts#L5

[WilliamBergamin]

This looks good 💯

I think I overlooked the assert statements in the original contribution for this, asserting against internal fields can lead to issues, we don't want this to become a pattern in the project 😅

We might want to set up a "mock server" make a request to it using say_stream and capture the arguments 🤔 there might also be a simpler way to do this as well

[WilliamBergamin]

I think I overlooked how these asserts are expecting internal arguments, if you find a better solution to please contribute it 🙏 We don't want this to become a pattern in the project 😅

[WilliamBergamin]

We might need to set up a mock web server and capture the request sent to it 🤔

[zimeg]

@WilliamBergamin I'll hold off on merging this to find these preferred patterns! Super appreciate the second thought toward this 🧠 💡

[WilliamBergamin]

@zimeg I sent a commit on this branch to improve how we test say_stream configurations and not rely on the internals of our dependencies

[mwbrooks]

✅ Thanks for putting this together @zimeg!