Currently, only customSessionID can be customized when hitting my custom LLM endpoint, forcing me to concatenate multiple pieces of information into this single field (e.g., user_id|hume_chat_group_id). I plan to include even more data in the future, which will quickly become unruly. Please support an explicit metadata object alongside requests to manage this more cleanly.