Update translations

Editor assessment

Acceptable, but thin on specifics for a translation commit. 'chore: update translations' is imperative and clean yet drops both the i18n scope and the target tree ('docs', 'learn', 'client') that the repo's sync convention normally includes, making this one harder to place in filtered history; was it a cross-cutting sync? The subject is at least honest and short, with the PR reference carrying the details. No body is needed for a bulk sync and none is present, and no breaking markers appear, correctly. The imperative 'update' also departs from the past-tense 'processed' phrasing the repo tends to use for these syncs, a small inconsistency in house style. Structurally valid; the loss is purely navigational.