Bulk-send MCP tools now enforce the 200-id batch limit

The four bulk-send tools documented a maximum of 200 ids per call but did not enforce it: a larger batch was accepted and every email was sent. They now reject it, exactly as the REST routes always have. See the tool catalog and Bulk operations.

• A call with more than 200 ids that used to succeed now returns an error and sends nothing — no email, no queued job. bulk_send_invoices, bulk_send_quotes, bulk_send_proformas and bulk_send_delivery_notes check the batch before dispatching anything, so the rejection costs the recipient nothing. Split the call into blocks of 200 and repeat it. The message names the limit and what you sent, and no id of the batch: No puedes enviar más de 200 facturas por lote. Has enviado 201. Divide el lote en bloques de 200 como máximo y repite la llamada.
• The REST endpoints are unchanged. POST /v1/{resource}/bulk-send already rejected oversized batches with 422, error.code: "invalid_param_value" and error.param: "ids", and still does. There is no new error code, no new header and no 429: the limit is on the size of one payload, not on how often you call. Scopes, rate-limit category and the BulkPartialSuccessResult response shape do not move either.