Fix tool calls in chat

[neoxelox]

chain-complete was returning tool calls stringified as a content type text instead of content type tool-call

{
  "type": "chain-complete",
  "config": {
    "provider": "OpenAI",
    "model": "gpt-4o-mini",
    "temperature": 0.1,
    "tools": {
      "get_the_weather": {
        "description": "Retrieves the current weather for a specified location.",
        "parameters": {
          "type": "object",
          "properties": {
            "location": { "type": "string", "description": "The city and country, e.g., 'Valencia, Spain'." }
          },
          "required": ["location"],
          "additionalProperties": false
        }
      }
    }
  },
  "response": {
    "streamType": "text",
    "text": "",
    "usage": { "promptTokens": 110, "completionTokens": 17, "totalTokens": 127 },
    "toolCalls": [
      {
        "id": "redacted",
        "name": "get_the_weather",
        "arguments": { "location": "Barcelona, Spain" }
      }
    ]
  },
  "messages": [
    {
      "role": "assistant",
      "toolCalls": [
        {
          "id": "redacted",
          "name": "get_the_weather",
          "arguments": { "location": "Barcelona, Spain" }
        }
      ],
      "content": "[\n  {\n    \"type\": \"tool-call\",\n    \"toolCallId\": \"redacted\",\n    \"toolName\": \"get_the_weather\",\n    \"args\": {\n      \"location\": \"Barcelona, Spain\"\n    }\n  }\n]"
    }
  ],
  "uuid": "redacted"
}

It also seems we were eating away a text message that came along with the tool call request:

There was also a bug that made us stuck when there was an error in the streaming chat:

Aaaand also fixed this error that appeared because we have tool calls defined in various fields with different arguments: toolCalls, inside content but with toolArguments and inside content too but with args: