… translations

- show the data-message provided by the error marker inside the error overlay
  (it was previously preserved by the core PRs but never consumed)
- only poll the thumbnail status for named thumbnail configurations, the
  editable config may also contain an inline configuration object
- stop polling while the browser tab is unfocused
- add the video.preview-in-progress translation to all remaining languages

The studio-backend video thumbnail status endpoint is now part of the committed
OpenAPI schema, so the asset API slice is generated with the
assetVideoThumbnailStatus query + VideoThumbnailStatus type. Drop the manual
injectEndpoints() hand-injection (and its hand-written types) from the enhanced
slice — the endpoint now comes straight from asset-api-slice.gen.ts.

Resolve assets/build/api/docs.jsonopenapi.json: take the latest 2025.4 schema
(which does not yet include the video thumbnail status endpoint) and re-add the
asset_video_thumbnail_status path + VideoThumbnailStatus schema on top, so the
generated asset slice keeps the endpoint. Build artifacts taken from 2025.4 (CI
regenerates them).

When the thumbnail finishes converting, the document state is unchanged (same
asset reference) — there is nothing to save, the editable just needs to
re-render. triggerSaveAndReload() runs an autosave, which the edit-lock gate
holds until the first user edit; for a poll-triggered save with no prior edit
that never resolves and the editor hangs on the reload overlay.

Add a reload-only path (DocumentApi.reloadIframe -> iframeRef.reload()) and use
it from the video editable. Avoids the autosave/edit-lock gate entirely and no
longer requires save permission for the auto-refresh.

reloadIframe now flushes pending edits first when the document is modified
(save-and-reload, as before — the edit-lock gate is already resolved in that
case), and only does a plain reload when there is nothing to save. Keeps the
original save-and-reload behavior where edits exist while still avoiding the
edit-lock autosave gate hang for the no-edit case (e.g. opening a document whose
video is already assigned and still converting).

…refresh

The video editable's auto-refresh chose save-vs-reload from the redux `modified`
flag, which is set via a deferred startTransition. A "finished" poll landing in the
brief window right after a keystroke saw modified=false and took the reload-only
path, discarding the just-typed (still unsaved) value.

Record edited documents synchronously in triggerValueChange instead. Any document
the user has touched is then always flushed via save-and-reload (which persists the
live editable values and whose edit-lock gate is/will-be resolved, so it cannot
hang), while never-edited documents keep the reload-only path. The flag is cleared
after a save-and-reload and on unregister so a freshly reloaded, untouched document
correctly reverts to reload-only.

Resolve conflict in video-editable.tsx: keep the renderEditButtonOverlay
refactor (ours) and adopt the InheritanceOverlay -> EditableOverlay rename
from 2025.4. Generated public/build artifacts taken from this branch; CI
regenerates them on push.

…ock gate

The gate is armed once on EditorContainer mount, not per iframe reload. The
delete still stands (the reloaded document is a clean baseline, so a later
refresh can take the cheap reload-only path), but the prior rationale was wrong.

't("video.edit")' had no translation key in any language (pre-existing), so the
tooltip showed the raw key. Reuse the generic 'edit' key, which is translated in
all 7 languages.