[Bug]: Rivet's "Node" executor requires Rosetta 2 but doesn't prompt

### What happened?

It appears that if you do not have Rosetta 2 installed on an M1/M2 Mac, and you attempt to use the Node executor, the "run" button never appears, and no errors or dialogs appear on screen. Digging into the Javascript console shows the error "Error running sidecar - Bad CPU type in executable (os error 86)".

It appears that Rivet's node binary is an Intel binary which requires Rosetta to be installed to work on M1/M2, but for some reason the ["you need to install Rosetta" window](https://support.apple.com/library/content/dam/edam/applecare/images/en_US/macos/Big-Sur/macos-big-sur-software-update-rosetta-alert.jpg) isn't opening.

Potential resolutions would be:

- Provide an arm64 "Apple Silicon" binary in the app (which will assumedly require changes to the build process)
- Or, check if the user is on Apple Silicon (`uname -m`) and if so, check if Rosetta is installed (`stat /Library/Apple/usr/share/rosetta/rosetta`) and if not, prompt the user to install it (or have a button offering to just install it by running `/usr/sbin/softwareupdate --install-rosetta --agree-to-license` or similar).

### What was the expected functionality?

The run button does not appear if Node is selected as the executor and Node cannot run due to architecture incompatibility. No error messages or indicator appears, so the user doesn't know why the Run button isn't showing up.

### Describe your environment

The user who first found this problem was on a 2021 14" MBP with M1 Pro and macOS 14.0

### Relevant log output

```shell
Error running sidecar - Bad CPU type in executable (os error 86)
```

### Relevant screenshots


### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

Start by reproducing the missing Run button with the Node executor on an Apple Silicon Mac without Rosetta, then inspect the JavaScript console for the reported sidecar error. Done means the app visibly explains the architecture problem and offers an appropriate resolution, such as prompting for Rosetta or using an Apple Silicon binary.

Written by the indexing model from the issue text.