"Failed to parse TTL for prepared query , ignoring" spamming the logs

[jameshartig]

Overview of the Issue

We are seeing hundreds of thousands of logs Failed to parse TTL for prepared query , ignoring after upgrading Consul.

This was caused by a typo in #20563 that didn't put that warn in an else block. That warning should also include the error message, right?

---

Reproduction Steps

Use prepared queries and v1.19.0

Consul info for both Client and Server

N/A but running v1.19.0

Operating system and Environment details

N/A

Log Fragments

2024-06-26T23:59:58.950Z [WARN]  agent.catalog-data-fetcher: Failed to parse TTL for prepared query , ignoring: ttl=1s prepared_query=publisher-api