[Bug]: t3 code forgets the used "--force-device-scale-factor" when it self-updates

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/web

Steps to reproduce

1. on a linux computer with a very high DPI screen, launch T3 code with "--force-device-scale-factor=X" (I launch it like this every time through a shell script)
2. wait until T3 Code notitices a pending T3 Code update (happens very often)
3. click the "update" + "relaunch" buttons
4. now T3 Code relaunches with tiny unreadable GUI because it re-launches itself without the --force-device-scale-factor=X parameter (it would be much nicer if it was smart enough to notice that it is launched using --force-device-scale-factor=X and then just also re-launched itself with that exact same --force-device-scale-factor=X parameter)

Expected behavior

it would be much nicer if it was smart enough to notice that it is launched using --force-device-scale-factor=X and then just also re-launched itself with that exact same --force-device-scale-factor=X parameter

Actual behavior

now T3 Code relaunches with tiny unreadable GUI because it re-launches itself without the --force-device-scale-factor=X parameter

Impact

Cosmetic issue

Version or commit

0.0.42

Environment

linux

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

restarting T3 Code again using your normal method with the desired --force-device-scale-factor=X parameter

Start in the apps/web self-update and relaunch flow, tracing how the application is started after an update. Reproduce the Linux case with --force-device-scale-factor=X, then verify that the relaunch preserves the exact argument and the GUI scale remains readable.