fix(osc): an unresolvable destination logs an error on every send and shows no row #369

What happens

An OSC destination whose host name does not resolve, used without an interface pin, fails to create its client on every send. Each attempt logs an ERROR ("Failed to create OSC client …"): a probe logged 600 lines for 600 sends, so a transmitter row streaming at its frame rate writes thousands of lines a minute and buries the log tail the diagnostics bundle carries. Because no client is ever created, the destination also gets no send-failure record, so neither the Operator Screen nor Statistics shows that this destination is not being reached.

Expected

A destination whose client cannot be created gets a retry delay and a send-failure record like any other failing destination: one log line per failure streak (with the periodic reminder), and a row naming the destination on the Operator Screen and in Statistics until it can be reached again.

Setup

All platforms, an OSC destination configured by a host name that the show network's resolver cannot answer, no interface pin. Found while reviewing the send-failure reporting for #322.