on-demand session conversation

[Mookse]

While it has ramifications in other tickets, the idea here is to limit traffic to Cosmos by only initiating a save conversation when someone has actually intentionally initiated one instead of session initialization itself; note: keep threads as -is, being requested from openai at start of conversation

• [x] front-end returns thread_id
• [x] removed conversation from session and factory
• [x] patchArrayItems altered
• [x] mChat, mRuns and mPrepareMessage refactor
• [x] added class-conversation-functions.mjs
• [x] enhanced conversation and message class extenders
• [x] refactored class-message-function.mjs

[Mookse]

session threads look good, something inside of messages, most likely because avatar is singular and is not always asking session

isnt having ! holding all of the messages (at avatar level) an inherent problem?

• solution is to create new avatar variant of Q for every session.... that's a lot of memory, or perhaps we can make a Q-exception - an extended sort of avatar for MyLife? In honesty, that might make sense, one that could keep all of its session messages separate, understandably, it's either in session or not, and this gives us some proxy server-like actions, like managing multiple conversations, whereas otherwise, avatars are themselves the primary conduit of conversation, but wait, what if yuo are the object that is being avatared? ergo, you must be able to hold multiple conversations as one avatar, so not only Q, but members and everyone... okay, that means that it's back at avatar level to manage BUT it can handle multiple conversations, that should be sufficient for all use cases - probably should do that in this ticket