fix: Fix incorrect exit code Update build.sh

[barajeel]

Pull Request type

Please add the labels corresponding to the type of changes your PR introduces:

• Feature
• Bugfix
• Refactor
• Format
• Documentation
• Testing
• Other:

Description

I’ve corrected an issue where the script was using exit 0 after displaying an error message. It’s more appropriate to use exit 1 to indicate that an error occurred, as a non-zero exit code is expected to signal failure.

Related Issues

This change ensures that the exit status reflects the actual outcome of the operation.

Checklist

• I have performed a self-review of my own code.
• The tests pass successfully with cargo test.
• The code was formatted with cargo fmt.
• The code compiles with no new warnings with cargo build --release and cargo build --release --features runtime-benchmarks.
• The code has no new warnings when using cargo clippy.
• If this change affects documented features or needs new documentation, I have created a PR with a documentation update.