Fixes the Linux build, which could not start at all, and the same latent fault
on macOS.
- Linux and macOS: the app starts. The NDI runtime is bundled right beside
the native addon, but the addon never looked there — it searched only absolute
paths that happen to exist on the build machine. On Linux that meant an
immediate crash (libndi.so.6: cannot open shared object file) on any machine
without the NDI SDK installed system-wide. On macOS it worked only if you
happened to have NDI Tools. Windows was never affected, because its DLL search
order already looks in the module's own directory. - The arm64 Windows and Linux packages are withdrawn. They paired an arm64
Electron binary with x86-64 NDI addons and could never have started. NDI's
Windows redistributable is x64/x86 only, so ARM64 Windows is not something
that can be supported at all. macOS keeps both architectures — use the x64
Windows build under emulation on an ARM64 machine. - A Linux client is reported as Linux, in the Control Deck and over the
automation API, instead of being labelled Windows. - Diagnostics report the running version. Logs from v1.1.0 claimed 1.0.0.
Tested on Windows 11 x64 and Ubuntu 24.04 x86_64.