fix: image rendering

[VladaHarbour]

No description provided.

[linear]

SD-60 Feature: Image handling

[github-actions]

Status: PASS

The key change — switching from .some() to .every() in the mc:Choice selection logic — is exactly what ECMA-376 Part 3 §10.2.2 requires:

"If the markup consumer does not understand all of the namespaces identified, it shall not select that Choice element. Markup consumers shall select the first Choice element, in markup order, in which all namespaces identified by the Requires attribute are understood."

The old .some() behavior was actually a spec violation: it would select a mc:Choice if even one of its required namespaces was supported, but the spec mandates every listed namespace must be understood before that choice can be selected. The PR corrects this.

The updated tests reflect the spec correctly:

• A choice with Requires="wps w14" (both understood) → selected. ✓
• A choice with Requires="wps unknownNs" (one unknown) → falls through to mc:Fallback. ✓

The utilities.ts/utilities.test.ts hunks in this diff are media path normalization changes unrelated to OOXML element semantics — nothing to flag there from a spec compliance angle.

For reference: https://ooxml.dev/spec?q=mc:Choice