Fix Studio updater on Windows

[nightnei]

Related issues

• Fixes STU-1069

Proposed Changes

With this PR we are starting using the new property (studioArch) to provide Studio's arch to Squirrel, since arch is patched by Squirrel and it fails arm64 Windows version updates.

Testing Instructions

1. Change Studio version in package.json to e.g. 1.6.2 and run npm i
2. Install and update Studio:

	Before update	After update
Windows (Parallels) npm run make:windows-arm64 Here we previously had bug, it was updated to Intel instead of Arm
Windows (Parallels) npm run make:windows-x64

3. Now let's switch to trunk (keep the changed package.json from the 1-st step) and repeat the same two commands for Windows to make sure that the nearest Studio release will work as expected. Keep in mind that currently Studio doesn't have the new studioArch property, so the nearest first release will still be updated incorrectly - switching from arm to intel version. But then all releases will be good, since Studio will use studioArch.
   3.1 Intel -> Intel
   3.2 Arm -> Intel (As was mentioned above, 1 release will still have bug)
4. macOS - testing macOS is more dificult than Windows (details - STU-1069#comment-db7c4f2b), so you can go just with this artifact which I build, it's enough to test only one this case, to confirm that everything works with studioArch and arch can be ignored.

[nightnei]

Just fixed tabs, nothing changed here

[ivan-ottinger]

I am going to review this PR.

[ivan-ottinger]

Thank you for the fix, Vova! The change looks good and I have tested all scenarios. The updates went well in all cases.

It took a bit longer as I run into issues with the build process (not related to the PR) and it took ages for the Windows builds to finish.

Windows

Update with the PR branch

ARM:

Before app update	After app update

Intel/AMD:

Before app update	After app update

Update with the trunk branch

ARM:

Before app update	After app update (gets updated to the incorrect architecture - as expected)

Intel/AMD:

Before app update	After app update

---

macOS

Using the provided build:

Before app update	After app update

[nightnei]

@ivan-ottinger , thank you so much for thorough testing ❤️

It took a bit longer as I run into issues with the build process (not related to the PR)

Same

it took ages for the Windows builds to finish

Yeah, build process on Windows really takes a lot of time in comparison with macOS. Additionally when you develop, testing and iterate 😅

Sorry that you spent a lot of time, and thanks for sharing my pain 😁🤗

[github-actions]

📊 Performance Test Results

Comparing 23188cd vs trunk

site-editor

Metric	trunk	23188cd	Diff	Change
load	9886.00 ms	10454.00 ms	+568.00 ms	🔴 5.7%

site-startup

Metric	trunk	23188cd	Diff	Change
siteCreation	17302.00 ms	19476.00 ms	+2174.00 ms	🔴 12.6%
siteStartup	6997.00 ms	8008.00 ms	+1011.00 ms	🔴 14.4%

---

Results are median values from multiple test runs.

Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change

[ivan-ottinger]

Sorry that you spent a lot of time, and thanks for sharing my pain 😁🤗

Hehe, no worries! I did other things while it was building. 😄