Handle out of memory and out of time limit issues gracefully

[rg20]

This PR adds two things:

1. Introduces a time limit for computing related variables. This function can take a lot of time for very large problems (in this case 20+ M variables). Ideally, we need to speed up this with a better algo and fine tune for larger problems
2. Catch std::bad_alloc exceptions in solve function. Currently, we only catch cuopt::logic_error

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[rg20]

/ok to test ab8d9d7

[chris-maes]

Should a bad_alloc be a cuopt::logic_error? We might want to create a different cuopt exception for this.

[rg20]

bad_alloc is thrown by rmm, unless we catch them somewhere and convert them to logic_error, which is what I am doing here

[rg20]

/ok to test 98411dd

[rg20]

/merge