Fix ignoring exit code from spawnSync - run-wrangler.js

[defjosiah]

Fixes #433
Fixes #335

I had some api key issues while publishing a route to a specific zone.
I realized that the npm "run-wrangler" wrapper, was exiting zero when our api key was incorrect,
when I expected it to exit non-zero.

Looks like "spawnSync" returns an explicit status field, which has to be propagated up in order to
have the correct exit status.

This diff fixes that (removes an unused import, and fixes some quotes).

Reproduction:

# add wrangler to package.json (yarn add @cloudflare/wrangler -D)
[email protected] CF_API_KEY=incorrect_api_key_here wrangler publish --release
echo $? # will be zero

After this fix

[email protected] CF_API_KEY=incorrect_api_key_here wrangler publish --release
# error Command failed with exit code 1.

[xortive]

Good work! Sounds like this fixes #335 as well. Thank you for the PR!

[ashleygwilliams]

this is excellent! thank you so much!

[EverlastingBugstopper]

Nice!

[defjosiah]

Happy to help! We were publishing using serverless framework before, wrangler is so nice 😀

[xortive]

QA tested the npm install, overwrites the run script successfully with the new one 👍