Make cargo build-dev produce a proper exit code

[tautschnig]

Description of changes:

Build failures of Kani-related components did not result in a non-zero exit code.

Resolved issues:

n/a

Related RFC:

n/a

Call-outs:

n/a

Testing:

• How is this change tested? Tested locally, see https://github.com/model-checking/kani/actions/runs/4753845746/jobs/8445926203 for an example that I had not previously noticed in my local builds.

• Is this a refactor change? No.

Checklist

• Each commit message has a non-empty body, explaining why the change was made
• n/a Methods or procedures are documented
• Regression or unit tests are included, or existing tests cover the modified code
• My PR is restricted to a single feature or bugfix

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

[adpaco-aws]

Thanks, @tautschnig ! Just a couple of minor comments.

If I'm not mistaken, this will prevent this error that @karkhaz had a while ago:

error: extern location for std does not exist: /home/runner/work/kani/kani/target/kani/lib/libstd.rlib

[tautschnig]

Thanks, @tautschnig ! Just a couple of minor comments.

If I'm not mistaken, this will prevent this error that @karkhaz had a while ago:

error: extern location for std does not exist: /home/runner/work/kani/kani/target/kani/lib/libstd.rlib

Indeed, I had very similar issues, and by now I've had them more than once...

[zhassan-aws]

Looks good.