fix(linux): initialize Compose display scaling

[veryCrunchy]

Summary

• initialize Compose Desktop's Swing globals before any desktop bootstrap path can enter Swing or AWT
• preserve automatic Linux DPI detection instead of hard-coding a scale factor
• make the process-start ordering deterministic and directly testable

Cause

Compose Desktop requires its global Swing configuration to run before Swing or AWT initialization when an application performs bootstrap work ahead of application. The desktop entry point installed diagnostics, handled update and single-instance states, and could open Swing dialogs before that ordering was explicit. On Linux Wayland/HiDPI sessions this can leave the process with incorrectly initialized display scaling.

Validation so far

On the dedicated build host:

• DesktopWindowActivationTest, including configure-before-launch ordering
• :ui:createDistributable

Both passed. This PR is temporarily a draft only while its own PR number is added to the user-facing changelog and the complete repository gate is run.

Scope

This does not force sun.java2d.uiScale, GDK_SCALE, or another fixed value. It enables Compose/Skiko's normal Linux auto-DPI initialization early enough to observe the actual desktop environment, including mixed-DPI setups.

[obiente-cloud]

Obiente preview

NC Native · 50a2fe735719 · Ready

Open preview

View in Obiente

_{Obiente updates this comment as the preview changes.}