.NET: Chat Message Storage Enhancements

[westey-m]

• Consider support for bootstrapping new threads where the user has a pre-existing database with chat history or an external id generator.
  • One option is agent.GetNewThread(new CustomMessageStore(dbClient, id)); but this may be painful to use if dbClient needs to be accessible everywhere GetNewThread is used.
  • Another option is allowing some arbitrary payload to be passed via GetNewThread to the message store factory, although this would not be strongly typed. (Added issue .NET: [Issue]: Consider using the FeatureCollections concept for passing arbitrary "services" to an Agent or AgentThread #3104 to continue looking into this)
• Consider creating custom messages stores at thread creation time from the factory, even if they may be removed after the first run in favor of a conversation id, to allow users to more easily update them if needed. (Since this is an alternative to item 1, it may be redundant).
• Consider supporting overriding the message store on a per run basis. (Added issue .NET: [Issue]: Consider using the FeatureCollections concept for passing arbitrary "services" to an Agent or AgentThread #3104 to continue looking into this)

[westey-m]

Moved making the factory methods async to a separate work item: #2520