macOS build should detect broken app-builder

[cwillisf]

Expected Behavior

If the version of app-builder used to build scratch-desktop will result in a broken mas or mas-dev build, the build process should inform the developer of the problem and refuse to build.

Actual Behavior

The build process completes despite a broken version of app-builder, resulting in a mas or mas-dev build that will crash on startup with a confusing error message. This can waste a lot of development and/or testing time, especially since the workaround requires easy-to-forget manual steps after every npm i or npm ci.

See also #120 and develar/app-builder#34

Steps to Reproduce

1. Clone the repository
2. Configure all the certificates and provisioning profiles necessary to build the mas and mas-dev targets.
   • This is non-trivial and only available to members of the Scratch Team.
3. Run npm run dist
4. Try to run the resulting application under dist/mas/ or dist/mas-dev/

Operating System and Browser

Affects macOS builds

[cwillisf]

One way to test is to have app-builder-bin modify a text-based plist file and then check to see if the plist file is still text, or has become binary. If the file becomes binary then the problem is present.