Channel returns 401 on ContinueConversationAsync calls #3245
Description
When a parent bot is deployed to multiple service instances and a skill responds to a different server instance than the one that was originally called by the bot service, attempting to send a message back to the channel returns a 401.
There are some inmemory objects and trusted URLs that are initialized when a bot is called from the channel for the first time. If a bot that hasn't been called from the channel gets a proactive message that executes ContinueConversationAsync, these objects are not there and the request fails.
Important: this issue doesn't repro on Emulator, you need WebChat to validate.
@axelsrz & @stevengum, we need to test this scenario in Python and JS to make sure there are no issues there.