Send a batch of topics to a destination (idempotent)

Body for the destination-scoped batch attach/detach.

The whole set moves in one request so the binding is written once, the sink connector is re-rendered once and one notification is sent — per-topic calls cost one Kafka Connect reconfiguration (and consumer-group rebalance) each.

The owning source is derived from the topic ids (source_<id>.<schema>.<table>); a set spanning more than one source is rejected, so no source id is carried here.

One (source, destination) managed binding, as seen from a topic.

binding_id is the managed pipeline id, usable to look up its pipeline metrics. topic_ids is the binding's full topic set, not just the topic the caller addressed.