Rethrow errors instead of returning FORCED_STOP

[odow]

Closes #156
Closes #157

@ikirill I didn't want to push new commits to your master branch, so I've cherry-picked your commits over to this branch.

[odow]

Bump. Any thoughts on this?

Here's another case where throwing an error would be helpful: https://discourse.julialang.org/t/nlopt-forced-stop-after-one-iteration-gradient-based-optimization/94383

[Vaibhavdixit02]

Bump, can we get this please will be a big Quality of Life improvement!

[stevengj]

Thanks for working on this; it would be good to have.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 70.00000% with 3 lines in your changes are missing coverage. Please review.

Project coverage is 69.07%. Comparing base (67acb7a) to head (8164ef3).

Files	Patch %	Lines
src/NLopt.jl	66.66%	3 Missing ⚠️

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #194      +/-   ##
==========================================
+ Coverage   68.83%   69.07%   +0.24%     
==========================================
  Files           2        2              
  Lines         799      802       +3     
==========================================
+ Hits          550      554       +4     
+ Misses        249      248       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[odow]

How's this now?

[ararslan]

This looks good to me, for whatever that's worth 😄

[Vaibhavdixit02]

I ran into this earlier today as well 😅

[odow]

I'll merge once CI has passed.