feat(bimi): reconcile the BIMI record to Cloudflare and keep it in step with the logo

The reconciler never wrote the BIMI record: only the console's verification
knew about it, so a stored logo was never published to the zone.

- SyncDnsRecordsInput carries the BIMI logo and certificate URLs; the record is
  created, updated (a= added or dropped) and, when the logo is removed,
  deleted. Only a record carrying this reconciler's comment is retired: one
  made by hand is left alone
- bimi.Publish decides the record in one place for the timer sweep, the
  console's button and the panel's verification. A held certificate is
  advertised only while it is valid for the logo being served: replacing the
  logo ends the certificate, and a record that kept naming it makes every
  receiver reject BIMI, including those that need no certificate
- saving or removing the logo or the certificate triggers the reconciliation in
  the background; the panel shows the record as the server writes it, says when
  a certificate is held back and why, and has a publish-now button
- a read error is not 'no logo': the sync leaves the record alone instead of
  deleting it over a database hiccup

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

services/webmail/messages/en.json

@@ -187,7 +187,13 @@
     "bimiError_noSize": "The SVG has no size (viewBox, or width and height), so it cannot be positioned.",
     "bimiError_empty": "No drawing could be found in that file.",
     "bimiError_notImage": "Choose a PNG or SVG file.",
-    "bimiError_tooComplex": "The drawing is too complex to fit in 32 KB."
+    "bimiError_tooComplex": "The drawing is too complex to fit in 32 KB.",
+    "bimiPublishNow": "Publish to DNS now",
+    "bimiPublishing": "Publishing...",
+    "bimiPublished": "Published to DNS: {created} created, {updated} updated, {deleted} removed.",
+    "bimiPublishUnavailable": "Publishing to DNS is not set up in this environment (the Cloudflare token is missing).",
+    "bimiAutoPublish": "When you save or remove the logo or the certificate, the record is published to DNS automatically.",
+    "bimiWithheld": "The stored certificate is not being advertised in DNS because it no longer applies to this logo ({reason}). Without it the record stays valid for providers that do not require a certificate."
   },
   "auth": {
     "adminLoginTitle": "Admin console",