Fix relationship XML error and add consumeServiceName

- Remove invalid relationship with duplicate type attributes
- Add consumeServiceName to SmtyLlmRequest SystemMessageType
- Framework will now use AgentServices.run#AgentTaskTurn for consuming LLM requests

@@ -26,12 +26,11 @@
     <moqui.service.message.SystemMessageType systemMessageTypeId="SmtyAgentTask" description="Agent Task"
     <moqui.service.message.SystemMessageType systemMessageTypeId="SmtyAgentTask" description="Agent Task"
         contentType="application/json"
         contentType="application/json"
         consumeServiceName="AgentServices.run#AgentTaskTurn"/>
         consumeServiceName="AgentServices.run#AgentTaskTurn"/>
-
-    <!-- Default AI Config (Brainfood VLLM) -->
-    <moqui.mcp.agent.ProductStoreAiConfig 
-        productStoreId="POPC_DEFAULT" aiConfigId="DEFAULT"
-        serviceTypeEnumId="AistVllm" description="Brainfood VLLM"
-        endpointUrl="http://crunchy.private.brainfood.com:11434/v1" apiKey="brainfood"
-        modelName="bf-ai" temperature="0.7" maxTokens="4096"/>
-
+    
+    <!-- LLM Request/Response Message Types -->
+    <moqui.service.message.SystemMessageType systemMessageTypeId="SmtyLlmRequest" description="LLM Request"
+        consumeServiceName="AgentServices.run#AgentTaskTurn"/>
+    
+    <moqui.service.message.SystemMessageType systemMessageTypeId="SmtyLlmResponse" description="LLM Response"/>
+    
 </entity-facade-xml>
 </entity-facade-xml>

@@ -42,7 +42,7 @@
         <field name="llmResponse" type="text-very-long">
         <field name="llmResponse" type="text-very-long">
             <description>Raw LLM response content (stored for audit/debug).</description>
             <description>Raw LLM response content (stored for audit/debug).</description>
         </field>
         </field>
- 
+  
         <relationship type="one" title="RequestedBy" related="mantle.party.Party">
         <relationship type="one" title="RequestedBy" related="mantle.party.Party">
             <key-map field-name="requestedByPartyId" related="partyId"/>
             <key-map field-name="requestedByPartyId" related="partyId"/>
         </relationship>
         </relationship>