[BUG] getaddrinfo EAI_AGAIN host error on ChatwootService when updating message source ID (v2.3.7)

Start by tracing the ChatwootService path that updates the message source ID and inspect how the configured Chatwoot URL becomes the hostname. Reproduce the update failure in the Docker Compose environment while checking the container logs and DNS behavior. Done means the request uses the configured Chatwoot hostname instead of the literal "host" and messages no longer appear as failed in Chatwoot.

Describe the bug When sending messages through an instance integrated with Chatwoot, the Evolution API intermittently fails to update the message source ID back to Chatwoot, throwing a DNS resolution error where the hostname being resolved is literally the string "host" instead of the actual configured Chatwoot URL.

Error log

[ChatwootService] Error updating Chatwoot message source ID: Error: getaddrinfo EAI_AGAIN host
To Reproduce Configure an instance with Chatwoot integration (valid URL, account ID, and token confirmed correct in Evolution Manager); send messages through WhatsApp normally; observe that messages are delivered successfully on WhatsApp, but Chatwoot occasionally shows "Falha ao enviar" (Failed to send) status on messages, including on internal system messages such as "Connection successfully established!"; check evolution-api container logs around the time of failure.

Expected behavior The Chatwoot message source ID update should use the actual configured Chatwoot base URL/hostname, not a literal placeholder string "host".

Environment Evolution API version: v2.3.7 (Docker image evoapicloud/evolution-api:v2.3.7); deployment: Docker Compose via Dokploy; database: PostgreSQL 15; cache: Redis 7; Chatwoot integration enabled with valid URL, account ID and token (confirmed correct in Manager UI).

Additional context Manually tested DNS resolution inside the container: getent hosts chatwoot resolves correctly to the internal Docker network IP; getent hosts host fails to resolve (as expected, since "host" is not a valid hostname), confirming the container's DNS/networking is healthy and the issue is isolated to this specific code path using a literal "host" string instead of the configured variable.

Impact Message delivery itself is not affected (messages reach WhatsApp normally), but Chatwoot UI incorrectly displays messages as failed, causing confusion for support agents.

Pode copiar esse texto direto para o campo de nova Issue no GitHub. Se quiser, também posso ajudar a montar os prints e o trecho do log como anexos para reforçar o relato.