Check feasibility following solution attempt

[jGaboardi]

This PR addresses #238 by adding a check_status() method within LocateSolver the is collected directly after a solution attempt in each model's respective solve() methods. It raises a RuntimeError if the status is anything but optimal. Tests for infeasibility are also updated.

xref #238, #237

cc @qszhao

[codecov]

Codecov Report

Merging #239 (f11a334) into main (18366f7) will increase coverage by 0.3%.
The diff coverage is 100.0%.

@@           Coverage Diff           @@
##            main    #239     +/-   ##
=======================================
+ Coverage   65.9%   66.3%   +0.3%     
=======================================
  Files         23      23             
  Lines       2554    2564     +10     
  Branches     559     560      +1     
=======================================
+ Hits        1684    1699     +15     
+ Misses       788     779      -9     
- Partials      82      86      +4     

Impacted Files	Coverage Δ
spopt/locate/base.py	96.3% <100.0%> (+0.2%)	⬆️
spopt/locate/coverage.py	100.0% <100.0%> (ø)
spopt/locate/p_center.py	100.0% <100.0%> (ø)
spopt/locate/p_median.py	100.0% <100.0%> (ø)
spopt/_version.py	33.8% <0.0%> (+1.5%)	⬆️

[gegen07]

@jGaboardi Sorry for adding commits to your pull request. I just changed the parameter name max_coverage to service_radius and reran all locate notebooks.

[jGaboardi]

@jGaboardi Sorry for adding commits to your pull request. I just changed the parameter name max_coverage to service_radius and reran all locate notebooks.

No problem! All looks good!