Set DPI awareness for chromium_subp to "System Aware"

[pstuecker]

By default Chromium enables the "PerMonitorV2" strategy for high DPI awareness. SWT instead defaults to "System" awareness as it does not yet support per monitor scaling (eclipse-platform/eclipse.platform.swt#131).

This leads to a mismatch in DPI settings between the Chromium render process (chromium_subp) and the host process (SWT application). If the browser widget is created on one monitor and then moved to another monitor, SWT does not rescale, but the Chromium render process does. This results in Chromium delivering a "too large" screen texture to SWT, which in turn results in strange visual artrifacts in the SWT application.

This PR forces chromium_subp to also use System Aware DPI scaling. If SWT supports PerMonitor scaling in the future, we'll have to adapt.

[github-actions]

License summary

❌ Not yet vetted dependencies:

Dependency	License	Status	Ticket
-/-/-/chromium/113.0.5672.93	unknown	restricted	none
-/-/chromiumembedded/cef/113.1.5	unknown	restricted	none

• Committers can request a license review via by commenting /request-license-review.
• After all reviews have concluded, Committers can re-run the license-vetting check by commenting /license-check

Workflow run (with attached summary files):
https://github.com/eclipse-set/browser/actions/runs/6821292172