Image editor saves referenced dotAsset in the UI session language instead of the asset's own language

Problem Statement

When an Image field references a dotAsset that exists in a non-default language (e.g., Spanish), the field never surfaces the language-specific version of that asset — regardless of whether the contentlet is opened in the asset's language or in the default language.

In the scenario tested: a dotAsset was created in Spanish and referenced by an "ImageEditorQA" contentlet. The Spanish version of the dotAsset was never shown or selectable from the Image field — not when the contentlet was opened under the English UI session, and not when opened under the Spanish UI session. The field appears to always resolve the referenced dotAsset to its default-language version, ignoring the asset's actual language.

Steps to Reproduce

Setup:

1. Admin logs in; confirms a non-default language exists (e.g., Spanish); notes its language ID.
2. Creates a dotAsset in the Spanish language; uploads a PNG image; publishes it ("Spanish-Asset").
3. Creates an "ImageEditorQA" contentlet with an Image field referencing the Spanish dotAsset.

Execution:
4. Open the ImageEditorQA contentlet with the UI language set to English.
5. Observe the Image field — the Spanish dotAsset version is not shown.
6. Switch the UI language to Spanish and open the same contentlet.
7. Observe the Image field again.

• Expected: The Image field displays the Spanish version of the referenced dotAsset when the UI language matches the asset's language; saving creates a new version of the Spanish asset.
• Actual: The Spanish version of the dotAsset is never shown in either context. The field does not reflect the asset's own language version regardless of the active UI session language.

Acceptance Criteria

• When an Image field references a dotAsset that has a version in language X, opening the contentlet in language X displays that language-specific version of the dotAsset
• Saving an edited image creates a new version of the dotAsset in the asset's own language, not the UI session language
• The behavior is consistent regardless of which UI session language is active

dotCMS Version

Latest from main branch (post #36363)

Severity

High - Major functionality broken

Links

• Related to #36363
• Test plan: 36363-36406-test-plan.md

Start by tracing how the Image field resolves a referenced dotAsset when the contentlet and UI session use different languages. Use the Spanish-asset reproduction and the linked 36363-36406 test plan to verify that the language-specific version is displayed and that saving creates a new version in the asset's own language under both UI-language contexts.