Comprehensive way to manage ReSolve configuration parameters

[pelesh]

ReSolve includes several different linear solvers and supports three hardware backends. There is a large number of parameters in ReSolve to select specific solution strategy and to tune its performance. Many of the parameters are specific to a specific solver type or hardware backend or both. We need a hierarchical method to allow user to configure ReSolve easily without sifting through dozens of (often cryptically described) parameters. Most of these parameters need to be set at runtime.

This issue is to start discussion how to handle this most effectively.

The issue originally raised by @kswirydo in #86 (comment)_

[pelesh]

Another part of this discussion is how to implement interface to ReSolve's select-from-the-list options. Currently we are just passing strings as this is quick'n'dirty way to set those options and get everything running. Perhaps a better way is to expose those lists to users in a form of enums. This will require some thinking about the scope in which these enums will live.

See how we handled similar issue in #12.

Also suggested by @kswirydo in #86 (comment)_