- Finish editing of Specialists with overview, agent - task - tool editor

- Split differrent caching mechanisms (types, version tree, config) into different cachers
- Improve resource usage on starting components, and correct gevent usage
- Refine repopack usage for eveai_app (too large)
- Change nginx dockerfile to allow for specialist overviews being served statically

config/tasks/EMAIL_LEAD_DRAFTING_TASK/1.0.0.yaml

@@ -1,6 +1,6 @@
 version: "1.0.0"
 name: "Email Lead Draft Creation"
-description: >
+task_description: >
   Craft a highly personalized email using the lead's name, job title, company information, and any relevant personal or 
   company achievements when available. The email should speak directly to the lead's interests and the needs
   of their company.

config/tasks/EMAIL_LEAD_ENGAGEMENT_TASK/1.0.0.yaml

@@ -1,6 +1,6 @@
 version: "1.0.0"
 name: "Email Lead Engagement Creation"
-description: >
+task_description: >
   Review a personalized email and optimize it with strong CTAs and engagement hooks. Keep in mind that this email is
   the consequence of a first conversation. 
   Don't use any salutations or closing remarks, nor too complex sentences. Keep it short and to the point.

config/tasks/IDENTIFICATION_DETECTION_TASK/1.0.0.yaml

@@ -1,6 +1,6 @@
 version: "1.0.0"
 name: "Identification Gathering"
-description: >
+task_description: >
   Detect and pass on identification information in the ongoing conversation, from within the following information:
     {question}
   Add to or refine the following already gathered identification information (between triple $)

config/tasks/IDENTIFICATION_QUESTIONS_TASK/1.0.0.yaml

@@ -1,6 +1,6 @@
 version: "1.0.0"
 name: "Define Identification Questions"
-description: >
+task_description: >
   Ask questions to complete or confirm the identification information gathered.
   Current Identification Information:
     $$${Identification}$$$

config/tasks/RAG_TASK/1.0.0.yaml

@@ -1,6 +1,6 @@
 version: "1.0.0"
 name: "RAG Task"
-description: >
+task_description: >
   Answer the question based on the following context, delimited between triple backquotes, and taking into account
   the history of the discussion, in between triple %
   {custom_description}

config/tasks/SPIN_DETECT_TASK/1.0.0.yaml

@@ -1,6 +1,6 @@
 version: "1.0.0"
 name: "SPIN Information Detection"
-description: >
+task_description: >
   Detect the SPIN-context, taking into account the history of the discussion (in between triple %) with main focus on 
   the latest reply (which can contain answers on previously asked questions by the user). Do not remove elements from
   the known SPIN (in between triple $) analysis unless explicitly stated by the end user in the latest reply. In all other cases, refine the

config/tasks/SPIN_QUESTIONS_TASK/1.0.0.yaml

@@ -1,6 +1,6 @@
 version: "1.0.0"
 name: "SPIN Question Identification"
-description: >
+task_description: >
   Define, taking into account the history of the discussion (in between triple %), the latest reply and the currently 
   known SPIN-elements (in between triple $), the top questions that need to be asked to understand the full SPIN context
   of the customer. If you think this user could be a potential customer, please indicate so.