In regards to the token argument. Have you observed a usage pattern where a user would want to pass a authentication token to the chat object as a string? From my understanding, you would need to have an extremely long lived token for this approach to be useful, which is not typical? I think this would also fail on Connect, when using the Integration approach, since Azure Integration would handle updating the token for you, but the chat object would not update.

I guess you could find the token in the chat environment and update it, but that doesn't seem like the right approach? Maybe it would be best to just remove the token argument, and just keep api_key and credentials.

Originally posted by @SokolovAnatoliy in #248 (comment)

Deprecating the token parameter the "right" way will require pulling in the lifecycle package, too.