Seemless data update: separate data manager from chatbot

[haozturk]

Inserting/updating/deleting certain data sources requires the restart of the chatbot container which introduces chatbot service downtime. Specifically, adding inserting/updating/deleting input lists or triggering fetching of new JIRA tickets can't be done without a restart.

@hassan11196 initially suggested separating data fetching and insertion into chromadb from the chatbot server. I can imagine a data manager container which handles data fetching and insertion into chromadb. While chatbot only reads from chromadb. After this, we can implement certain functionalities to data manager which allows easy data updates.