Resolve a messaging chat id

POST /v1/gateway/providers/:id/resolve-chat-id

Look up the chat id the configured bot should send to, using the token the gateway already holds — the caller never needs it. Telegram only; any other provider id returns 404. Reports the current state and returns rather than blocking, so the caller polls: found carries the id, awaiting_start means the user has not messaged the bot yet, conflict means the running daemon owns Telegram's getUpdates (keep polling — a message the user sends reaches the resolver through the daemon), invalid_token means no usable token is saved.

Response body

{ "status": "found", "chatId": "42", "username": "my_bot" }