[BUG] Invalid bounds need to return infeasible solution rather than erroring invalid bound

[rgsl888prabhu]

Describe the bug
Consider a scenario where lower bound is > upper bound, in this case when you try to set value, you get error invalid bounds.

{"CUOPT_ERROR_TYPE": "ValidationError", "msg": "Variable bounds are invalid"}

Steps/Code to reproduce bug
Test file

test.zip

This can't be reproduced through cli or with mps

Expected behavior
Should return infeasible

[aliceb-nv]

@rgsl888prabhu
Just to be clear: what is the expected result from the C API side? a CUOPT_VALIDATION_ERROR at problem creation, or a CUOPT_TERIMINATION_STATUS_INFEASIBLE after cuOptSolve?

[rgsl888prabhu]

@aliceb-nv It is expected to error with infeasible, @chris-maes @rg20 please correct me if I am wrong.

[rg20]

@aliceb-nv it should be CUOPT_TERMINATION_STATUS_INFEASIBLE